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] |
IMHO, the hackery that Crosstool employs to handle the libgcc_eh.a situation is very much unnecessary. A much simpler solution exists.. and that is to simply create a symlink:
libgcc_eh.a -> libgcc.a
after the first cross GCC is built and installed.
The technique is used by at least:
- Janis Johnson's `buildtools' scripts [1] - Alan Modra'a `recipe' script [2] - Alexandre Oliva [3] - my very own DIY Linux Reference Build [4]
Only 2 of the above refer to cross builds but the core problem is identical. I'm also developing a simplified cross building procedure (so far unpublished) where it works fine there too.. Some detailed rationale discussion can be found here:
http://www.diy-linux.org/pipermail/diy-linux-dev/2005-June/000556.html
Crosstool's logic could be greatly simplified were you to adopt the technique (IMHO of course).
1. ftp://ftp.linuxppc64.org/pub/people/janis/ 2. http://gcc.gnu.org/ml/gcc-patches/2005-05/msg02811.html 3. http://gcc.gnu.org/ml/gcc-patches/2005-02/msg00591.html 4. http://www.diy-linux.org/x86-reference-build/
Patches gratefully accepted any time. - Dan
------ 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] |