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] |
> cnelson@nycap.rr.com wrote: > > Crosstool looks useful and interesting. Thanks. I'm sorry if e- > > mailing> you directly is not the most appropriate way to ask this > > question but I didn't find a crosstool mailing list or anything. > > Use <crossgcc@sources.redhat.com>. I'm cc'ing that list. OK. Thanks. > > I'm trying to build G++ 2.95.3 on and for Intel Linux targeting PPC > > Linux. I got crosstool and it got the tgzs but after an hour or so, > > crosstool ends with: > > > > + cd /opt/crosstool/gcc-2.95.3-glibc-2.2.2/powerpc-750-linux-gnu > > + sh /home/chrisn/g++/crosstool-0.38/masq.sh > > + cd /home/chrisn/g++/crosstool-0.38 > > + gcc fix-embedded-paths.c -o > > /opt/crosstool/gcc-2.95.3-glibc-2.2.2/powerpc-750-linux- > gnu/bin/fix-embedded-paths > > fix-embedded-paths.c: In function `testit': > > fix-embedded-paths.c:377: initializer element is not constant > > fix-embedded-paths.c:377: (near initialization for > > `all_tests[2].old_oldrootlen') > > > > I found a strlen() at that location and replaced it with a > > literal but this seem strange. > > The literal is ok. Yeah, screwy code on my part! (Which version of > gcc complained about that error? I want all versions to do so!) If it's part of something crosstool already built, I don't know. I was building with demo-ppc750.sh. If it's the gcc on my path, that's: # gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/2.96/specs gcc version 2.96 20000731 (Red Hat Linux 7.3 2.96-110) > > Now my question: I want to build on Intel Linux for host Intel > > Windows and target PPC Linux. That's a "Canadian Cross," right? > > Your notes say that demo-canadian.sh isn't done but it's hard > > to tell if the notes or the script are more recent. Any guidance? > > I don't support host 'windows' directly. Is cygwin ok? Yes. > If that's what you want, you'll first need to find > a Linux -> Cygwin cross compiler. I haven't played > around with that. Any reason you can't build the > compilers on Cygwin? I'm not sure I've got Cygwin, I don't play with imitation UNIX much. I'm building tools for someone else. ------ 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] |