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: crosstool under Cygwin


Michael D. Miller wrote:
Sorry for the direct contact - I'm having system configuration issues that are not allowing me to post to your thread.
I am using version 0.20 of the crosstool chain on a SH4 processor (7750R) with some success.

Have you booted a kernel built with it yet? BTW I'm about to release 0.22 which removes glibc-2.3.2-patches/sh-fpscr-libc-kludge.patch since it caused the following gcc tests to fail on sh4: 20000605-1.c 20020411-1.c 930603-1.c complex-6.c conversion.c gofast.c ieee/20010114-2.c ieee/inf-1.c ieee/rbug.c ieee/20010114-2.c ieee/inf-1.c ieee/rbug.c

> I also tried to build on a machine with the
latest Cygwin, using the latest 0.21 version. You are correct about the CR vs. CRLF causing the problems that Sangmoon saw. However, I was still unable to build glibc. The problem I ran into was during the link I got undefined errors like:
: undefined reference to `__GI_getenv'
/cygdrive/f/cygwin/crosstool/crosstool-0.21/build/sh4-unknown-linux-gnu/gcc-3.3.1-glibc-2.3.2/build-glibc/libc_pic.os(.text+0x66f28): In function `glob64':
: undefined reference to `__GI_qsort'
/cygdrive/f/cygwin/crosstool/crosstool-0.21/build/sh4-unknown-linux-gnu/gcc-3.3.1-glibc-2.3.2/build-glibc/libc_pic.os(.text+0x67d00):

Sounds nasty. I haven't seen those errors myself. For what it's worth, here's where those functions live in my copy on linux:

./linuxthreads/libc_pic_lite.a:msort.os:00000160 T __GI_qsort
./linuxthreads/libc_pic_lite.os:00013368 T __GI_qsort
./libc_pic.a:msort.os:00000160 T __GI_qsort
./stdlib/msort.os:00000160 T __GI_qsort

You might want to post the actual command that was being run.

I have already tried update gcc to 3.3.1 under Cygwin. The build worked OK, but (as expected) had no effect on the link problems. I suspect a newlib/glibc issue may be the cause, and will try building a glibc for Cygwin tonight. In any case, I do plan to spend some time trying to get the crosstools running under Cygwin.

Thanks, lots of people are interested in Cygwin support!


On a side note, I had a minor problem with the path export in crosstool.sh because my Windows path contained "Microsoft Visual Studio" as a string. I worked around the issue by changing the line to add quotes around the PATH environment variable:
export PATH=${PREFIX}/bin:"${PATH}"
Please consider this potential change to your scripts.

Thanks, I'll add it! - Dan

--
Dan Kegel
http://www.kegel.com
http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045


------ 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]