WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki
« previous next »
Pages: [1]   Go Down

Author Topic: Compiling environment  (Read 3329 times)

Offline meo

  • Hero Member
  • *****
  • Posts: 651
Compiling environment
« on: August 06, 2009, 01:40:59 PM »
Hi guys!

What would be the ultimate (in realistic terms) compiling environment? Considering extensions, RAM-memory, swapspace etc. Suggestions will be very appreciated.

Have fun,
meo
Logged
"All that is very well," answered Candide, "but let us cultivate our garden." - Francois-Marie Arouet Voltaire

Online Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 14820
Re: Compiling environment
« Reply #1 on: August 07, 2009, 04:37:35 AM »
If you load the following as tcz extensions, they will not use much ram and will take care of most compiling situations:

gcc, binutils, base-devs, bison, diffutils, file, findutils, flex, gawk, gperf, grep, m4, make, patch, pkg-config, sed

You may also need the following perl based extensions, but this is less likely:

perl_xml, perl_archive_zip, help2man
Logged

Offline meo

  • Hero Member
  • *****
  • Posts: 651
Re: Compiling environment
« Reply #2 on: August 07, 2009, 07:22:40 AM »
Hi Juanito!

Thanks for your suggestion. I know you have been working your ass off to get openoffice compiled for tinycore. I hope you get some suggestions to get around the snags. I really appreciate your work and your suggestions.

Have fun extending tinycore,
meo
Logged
"All that is very well," answered Candide, "but let us cultivate our garden." - Francois-Marie Arouet Voltaire

Online Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 14820
Re: Compiling environment
« Reply #3 on: August 07, 2009, 07:25:00 AM »
Just  to be sure there's no misunderstanding, an openoffice-2.3.1 extension is alread available as oo2.tcel/tczl.

It was openoffice-3.1 that I was trying and failing to compile...
Logged

Offline meo

  • Hero Member
  • *****
  • Posts: 651
Re: Compiling environment
« Reply #4 on: August 07, 2009, 07:45:36 AM »
Hi again!

I'm aware of that but thanks anyway!

Have fun,
meo
Logged
"All that is very well," answered Candide, "but let us cultivate our garden." - Francois-Marie Arouet Voltaire

Offline 3rail

  • Full Member
  • ***
  • Posts: 114
Re: Compiling environment
« Reply #5 on: August 09, 2009, 06:09:21 PM »
Quote from: Juanito on August 07, 2009, 04:37:35 AM
If you load the following as tcz extensions, they will not use much ram and will take care of most compiling situations:

gcc, binutils, base-devs, bison, diffutils, file, findutils, flex, gawk, gperf, grep, m4, make, patch, pkg-config, sed

You may also need the following perl based extensions, but this is less likely:

perl_xml, perl_archive_zip, help2man


What's the overlap between these and "compiletc"

TIA
Logged

Offline ^thehatsrule^

  • Retired Admins
  • Hero Member
  • *****
  • Posts: 1726
Re: Compiling environment
« Reply #6 on: August 09, 2009, 08:34:03 PM »
It contains all of the one on the "first line" (or see the .dep)
Logged

Online Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 14820
Re: Compiling environment
« Reply #7 on: August 10, 2009, 02:00:35 AM »
compiletc is for tinycore version 1.x, that lot is for tinycore version 2.x
Logged

Offline 3rail

  • Full Member
  • ***
  • Posts: 114
Re: Compiling environment
« Reply #8 on: August 10, 2009, 10:50:12 AM »
Quote from: Juanito on August 10, 2009, 02:00:35 AM
compiletc is for tinycore version 1.x, that lot is for tinycore version 2.x

I don't follow -- there's a compiletc for 2.x as well.
Logged

Offline ^thehatsrule^

  • Retired Admins
  • Hero Member
  • *****
  • Posts: 1726
Re: Compiling environment
« Reply #9 on: August 10, 2009, 12:36:53 PM »
They're different (see the .info)

For the record, my previous post was for the 2.x one.
Logged
Pages: [1]   Go Up
« previous next »