--- Comment #5 from pinskia at gcc dot gnu dot org 2006-03-18 06:20 ---
crosstools and the crossgcc list is the best place to ask questions like this
really.
Second sysroot can be changed at runtime now. So this is not a bug and closing
as such.
--
pinskia at gcc dot gnu dot org ch
--- Additional Comments From jlm_devel at laposte dot net 2005-06-01 17:35
---
this issue is solved if and only if BOTH configure options are set :
--with-local-prefix=$DESTDIR_BCKP
--with-sysroot=$DESTDIR_BCKP
specifying only where to find the headers isn't enough
but the error
--- Additional Comments From jlm_devel at laposte dot net 2005-05-21 18:22
---
I re-checked to be sure... and I confirm :
$ make all-gcc
...
$ echo $?
2
$ cd gcc
$ make all
...
$ echo $?
0
$ ls libgcc.a
libgcc.a
so the issue is : two make that should have the same behaviour don't
--
--- Additional Comments From jlm_devel at laposte dot net 2005-05-21 17:50
---
maybe, I can too using several workaround like crosstool.sh is doing but
this lead to have the target tree be located at the same place of the
crosschain which is a nonsens...
why a target filesystem's
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-05-21
15:43 ---
This does not make sense, people create cross compilers to x86_64-pc-linux-gnu
all the time.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21698
