This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Hello On Wed, Aug 17, 2011 at 13:47, Bryan Hundven <bryanhundven@gmail.com> wrote: > You can build crosstool-ng and run it from where you extracted/cloned it: > > $ ./configure --local > $ make Very interesting - thanks a lot for the tip ! On Wed, Aug 17, 2011 at 13:51, Yann E. MORIN <yann.morin.1998@anciens.enib.fr> wrote: > Well, really depends. I for one have to maintain some toolchains, test new > versions and/or settings, so it is nice to have crosstool-NG being acutally > installed, so I can simplu get rid of the build dirs with a simple 'rm -rf' > once I'm done with the current tests... It is also the case for a bunch of > other guys as well. > But sure, for a one-off toolchain build, actual install is probably > overkill, hence the --local switch. Of course - I just meant for people who just want to use the resulting toolchain, not maintaining the toolchains BTW I now have a .dmg containing binaries for basic GNU tools that allows to create a crosstool-ng on OSX, along with a basic shell script to start configure and ct-ng with the right options on the right prefixes. Would you be interested in releasing it on crosstool-ng website, for OSX users who want to quickly get into crosstools-ng with the macports step? -- vCard: http://guylhem.tel -- For unsubscribe information see http://sourceware.org/lists.html#faq
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |