This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more infromation.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Hello Joe, all, Ok, Well I have switched over to building gcc2.95.2 for the arm-elf target and have been relatively successful. I had to apply a patch to arm.h via the patch file off of the ecos site. But the bottom line is that it actually completed building in the cygwin environment. Now I am ready to test the compiler and created a quick void main(void){ } type of c program just to try the compiler. When I compile it it reports that it can't find crt0.o I know this get created as a result of building either newlib or uc-libc . Which one should I build, and what are the magic 3 or 4 lines needed to build them and make the compiler see the crt0.o file??? People tell me that I don't want to use newlib because it is too big. I did notice that if I kick off the uc-libc makefile it starts looking for linux header files. I didn't realize I needed linux support build in to the compiler library for building a void main(void) tiny elf file. I have appreciated all the help so far from everyone, and I hope someone can comment on these issues. Thanks, Dan -----Original Message----- From: Joe deBlaquiere [mailto:joe@wirespeed.com] Sent: Wednesday, July 12, 2000 1:14 PM To: uclinux-dev@uClinux.org Subject: RE: [uClinux-dev] ARM uCLinux and newlib You don't need to do anything with the arm-uc-libc package until you're ready to make some user applications. If you can't compile a kernel, don't worry about user apps ;o). There have been a few versions of the gcc stuff that I couldn't get to compile. If you're still having problems, the compiler in the directory http://www.uclinux.org/pub/uClinux/ports/arm/ is older, but generally pretty good. I haven't built it under cygwin thought I know 2.95.2 for arm-elf can be built under cygwin, and that seemed to be a kinda picky process ). --Joe > -----Original Message----- > From: owner-uclinux-dev@uClinux.org > [mailto:owner-uclinux-dev@uClinux.org]On Behalf Of Dan Carlson (EUS) > Sent: Wednesday, July 12, 2000 11:46 AM > To: 'uclinux-dev@uClinux.org' > Subject: RE: [uClinux-dev] ARM uCLinux and newlib > > > Vadim, Hello to all, > > Help! > > I still don't know what to do with the arm-uc-libc.tar.gz file on the > ARM7TDMI ucLinux site. Do I replace the libc directory in > newlib with the > files supplied by arm-uc-libc.tar.gz??? > > I have manually tried to compile the vfscanf.c file but the > same type of > error still occurs. Isn't there anyone else out there that > has had this > kind of "Subtraction of two symbols" error happen while building... > > /usr/build-egcs/gcc/xgcc -B/usr/build-egcs/gcc/ > -B/usr/build-egcs/arm-uclinux/ne > wlib/ -B/usr/local/arm-uclinux/bin/ -idirafter > /usr/build-egcs/arm-uclinux/newli > b/targ-include -idirafter /usr/egcs/newlib/libc/include > -nostdinc -g -O2 > -mdisa > ble-got -O2 -DABORT_PROVIDED -DHAVE_GETTIMEOFDAY -DARM_RDP_MONITOR > -fno-builtin > -I/usr/build-egcs/arm-uclinux/newlib/./targ-include > -I/usr/newlib-1.8.1/newlib/ > ./libc/include -c ../../../../../../egcs/newlib/libc/stdio/vfscanf.c > C:\TEMP/ccDpnFvl.s: Assembler messages: > C:\TEMP/ccDpnFvl.s:1971: Error: Subtraction of two symbols in > different > sections > "strtol" {*UND* section} - ".L44" {*UND* section} at file > address 3892. > C:\TEMP/ccDpnFvl.s:1975: Error: Subtraction of two symbols in > different > sections > "strtoul" {*UND* section} - ".L54" {*UND* section} at file > address 3908. > make[5]: *** [vfscanf.o] Error 1 > make[5]: Leaving directory > `/usr/build-egcs/arm-uclinux/pic/newlib/libc/stdio' > make[4]: *** [stdio/lib.a] Error 1 > make[4]: Leaving directory > `/usr/build-egcs/arm-uclinux/pic/newlib/libc' > make[3]: *** [libc/libc.a] Error 2 > make[3]: Leaving directory `/usr/build-egcs/arm-uclinux/pic/newlib' > make[2]: *** [multi-do] Error 1 > make[2]: Leaving directory `/usr/build-egcs/arm-uclinux/newlib' > make[1]: *** [all] Error 2 > make[1]: Leaving directory `/usr/build-egcs/arm-uclinux/newlib' > make: *** [all-target-newlib] Error 2 > > Maybe I should post this message in an egcs or cross compiler > newsgroup??? > > It seems to me that perhaps I could just skip compiling vfscanf.c ??? > > Can anyone suggest a distribution of egcs files that might > build easily in a > cygwin environment for the arm-elf or arm-uclinux target? > > Thanks > > Dan > > > > > -----Original Message----- > From: Vadim Lebedev [mailto:vlebedev@aplio.fr] > Sent: Wednesday, July 12, 2000 5:06 AM > To: uclinux-dev@uClinux.org > Subject: RE: [uClinux-dev] ARM uCLinux and newlib > > > > David > > Try to compile this file manually with -O1 instead of -O2 > > > Vadim > -----Original Message----- > From: owner-uclinux-dev@uClinux.org > [mailto:owner-uclinux-dev@uClinux.org]On Behalf Of Dan Carlson (EUS) > Sent: mardi 11 juillet 2000 21:44 > To: 'uclinux-dev@uClinux.org' > Subject: RE: [uClinux-dev] ARM uCLinux and newlib > > > Vadim, all, > > Thanks for the FAQ update. However, now I don't know how to > install the > arm-uc-libc.tar.gz file. I don't think it is mentioned in the FAQ. > > Things are getting farther in the build process and I have > run in to another > problem. The FAQ mentions things possibly going wrong while compiling > newlib. Some of the newlib files compiled. Then I had the > following go > wrong in newlib... > > /usr/build-egcs/gcc/xgcc -B/usr/build-egcs/gcc/ > -B/usr/build-egcs/arm-uclinux/ne > wlib/ -B/usr/local/arm-uclinux/bin/ -idirafter > /usr/build-egcs/arm-uclinux/newli > b/targ-include -idirafter /usr/egcs/newlib/libc/include > -nostdinc -g -O2 > -mdisa > ble-got -O2 -DABORT_PROVIDED -DHAVE_GETTIMEOFDAY -DARM_RDP_MONITOR > -fno-builtin > -I/usr/build-egcs/arm-uclinux/newlib/./targ-include > -I/usr/newlib-1.8.1/newlib/ > ./libc/include -c ../../../../../../egcs/newlib/libc/stdio/vfscanf.c > C:\TEMP/cca6VjCL.s: Assembler messages: > C:\TEMP/cca6VjCL.s:1971: Error: Subtraction of two symbols in > different > sections > "strtol" {*UND* section} - ".L44" {*UND* section} at file > address 3892. > C:\TEMP/cca6VjCL.s:1975: Error: Subtraction of two symbols in > different > sections > "strtoul" {*UND* section} - ".L54" {*UND* section} at file > address 3908. > make[5]: *** [vfscanf.o] Error 1 > make[5]: Leaving directory > `/usr/build-egcs/arm-uclinux/pic/newlib/libc/stdio' > make[4]: *** [stdio/lib.a] Error 1 > make[4]: Leaving directory > `/usr/build-egcs/arm-uclinux/pic/newlib/libc' > make[3]: *** [libc/libc.a] Error 2 > make[3]: Leaving directory `/usr/build-egcs/arm-uclinux/pic/newlib' > make[2]: *** [multi-do] Error 1 > make[2]: Leaving directory `/usr/build-egcs/arm-uclinux/newlib' > make[1]: *** [all] Error 2 > make[1]: Leaving directory `/usr/build-egcs/arm-uclinux/newlib' > make: *** [all-target-newlib] Error 2 > > Could this be related to not having uC-libc installed??? > > Thanks anyone for your help. > > Dan > > > -----Original Message----- > From: Vadim Lebedev [mailto:vlebedev@aplio.fr] > Sent: Tuesday, July 11, 2000 12:46 PM > To: uclinux-dev@uClinux.org; uclinux-dev@geekcreek.net > Subject: RE: [uClinux-dev] ARM uCLinux and newlib > > > Hi Dan, > > I've just updated the FAQ to include corrected intsruction > how to build the > compiler > > Your problem is that you should create symlunks to libgloss > and newlibt in > the egcs > directory... The latest FAQ shows how to do it.... > > Of course you have to download and unzip the newlib tarball > from my site... > > > Vadim > > -----Original Message----- > From: owner-uclinux-dev@uClinux.org > [mailto:owner-uclinux-dev@uClinux.org]On Behalf Of Dan Carlson > Sent: lundi 10 juillet 2000 20:05 > To: uclinux-dev@geekcreek.net > Subject: [uClinux-dev] ARM uCLinux and newlib > > > Hello, > > I am having trouble building the cross compiler based on the > instructions > found on http://aplionet.aplio.fr/uclinux/uclinux-arm.htm and > I think it is > because I don't have newlib installed. This webpage does not > discuss how to > do that. Can anyone offer some suggestions? > > If you are familiar with the the build instructions found on > this at this > link you will notice that the targets defined for binutils > and egcs are for > target=arm-uclinux . Well, if I supply that same target for > the newlib > configure it tells me it is not a valid target. So I don't > know what to do. > Any help would be great. > > Dan ------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |