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] |
However, it seems I found another way to have the overall crosstool.sh script to succeed on my system. For all "gcc" configure phase (3 places in the crosstool script), I am "forcing" the as/ld binaries to use the following way (patch attached).
--with-gnu-as \ --with-as=${PREFIX}/bin/${TARGET}-as \ --with-gnu-ld \ --with-ld=${PREFIX}/bin/${TARGET}-ld \
Without this it looks like somewhere the wrong assembler or linker is chosen (on solaris) by the generated cross-compilers. Does this look bad or acceptable? How do you feel about it?
This allows the script to complete successfully on Solaris (and I guess on any other platform). I still have to test the resulting tool chain though.
It's a fine idea. Could you repeat your diff against a clean copy of crosstool? You seem to have a lot of extra stuff in your patch.
I might prefer to put those extra options in a shell variable if they get referenced a lot of places, and add a comment explaining why they're needed. - 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] |