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] |
That build directory is just where they sit before installation. I guess RESULT_TOP needs to be absolute?
Hi Dan,
I was trying to build a toolchain for an ARM9 processor with your crosstool and found what I think is a bug. I had modified one of the demo scripts by changing RESULT_TOP="../tools/crosstool". It ran for awhile, creating the path
../tools/crosstool/gcc-3.3.5-glibc-2.3.2/arm-unknown-linux-gnu/
as it was supposed to, but then it put all its build products in
build/arm-unknown-linux-gnu/gcc-3.3.5-glibc-2.3.2/
relative to the crosstool-0.43 directory I was running the script out of. I went back restored the value of RESULT_TOP to its original value of /opt/crosstool and reran the script. That time it ran fine, creating everything under /opt/crosstool like I assume it is supposed to.
Actually, it died while running testhello.sh because PATH_MAX wasn't defined, but I assume that is a different problem. It did finish building the entire toolchain.
BTW: I'm grateful to you for working this project - its very valuable. Thanks.
Jeff Cunningham Seattle, Washington
-- Wine for Windows ISVs: http://kegel.com/wine/isv
-- 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] |