This is the mail archive of the crossgcc@sources.redhat.com 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]

Re: using toolchain once it's built

From: Dan Kegel <dank at kegel dot com>
To: otto dot waltari at kolumbus dot fi, crossgcc <crossgcc at sources dot redhat dot com>
Date: Sun, 15 Aug 2004 15:02:11 -0700
Subject: Re: using toolchain once it's built
References: <20040814181129.YWJQ14814.fep19-app.kolumbus.fi@mta.imail.kolumbus.fi>

otto.waltari@kolumbus.fi wrote:

... the compilation succeeded without any problems. It created the directory trees under /opt/crosstools/, as supposed. But what now? Are they usable straight from there,

Yes.

or do I have to move include files and binaries to system wide locations?

No. No need to move anything.

This part was almost non-existent in your crosstools-howto. Perhaps you could make an addition to that doc, or something similar...

Yes, I should probably show how to use the resulting toolchain...

Oh yea, and I go with gcc-3.3.2-glibc-2.3.2, on top of Debian GNU/Linux with gcc 3.3.4.


Hmm, why 3.3.2 and not 3.3.4?
- Dan

--
My technical stuff: http://kegel.com
My politics: see http://www.misleader.org for examples of why I'm for regime change

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]