From: Ted L. <te...@la...> - 2005-02-12 05:07:58
|
So, I have been trying to get the tool chain to build under Cygwin, without much luck. Can anyone offer any ideas how to build the tool chain under Windows? Having to use a Linux box just so I can compile code for my gumstix seems excessive. Thanks, - Ted |
From: Craig H. <cr...@hu...> - 2005-02-12 05:22:12
|
On Feb 11, 2005, at 9:07 PM, Ted Larson wrote: > =A0So, I have been trying to get the tool chain to build under Cygwin,=20= > without much luck.=A0 Can anyone offer any ideas how to build the tool=20= > chain under Windows?=A0 Having to use a Linux box just so I can = compile=20 > code for my gumstix seems excessive. Of course, some people would say that having to pay $300 for an=20 operating system in order to use your desktop seems a little excessive=20= :) But you should be able to get things working under cygwin, if you=20 install the various tools that the buildroot needs. What's breaking? C |
From: Ted L. <te...@la...> - 2005-02-12 18:38:27
|
I admit, my first couple of tries to build were as a result of missing tools.like wget for example. =20 =20 Here is where I am stuck. --------->Build results Hunk #3 succeeded at 580 (offset 4 lines). touch /home/Ted/gumstix-buildroot/build_arm/mtd/Makefile mkdir -p /home/Ted/gumstix-buildroot/toolchain_build_arm #mkdir -p /home/Ted/gumstix-buildroot/build_arm/linux-2.6.10gum #rm -rf /home/Ted/gumstix-buildroot/build_arm/linux-2.6.10gum bzcat /home/Ted/gumstix-buildroot/sources/dl/linux-2.6.10.tar.bz2 | tar = -C /home /Ted/gumstix-buildroot/build_arm -xf - # Rename the dir from the downloaded version to the AFTER patch version mv -f /home/Ted/gumstix-buildroot/build_arm/linux-2.6.10 /home/Ted/gumstix-build root/build_arm/linux-2.6.10gum # Insert latest MTD code to kernel tree (cd /home/Ted/gumstix-buildroot/build_arm/mtd; sh patches/patchin.sh -2 = -y /home /Ted/gumstix-buildroot/build_arm/linux-2.6.10gum) patches/patchin.sh: 43: Syntax error: "(" unexpected make: *** = [/home/Ted/gumstix-buildroot/build_arm/linux-2.6.10gum/Makefile] Error 2 [Ted@Lion ~/gumstix-buildroot]$ =20 -----Original Message----- From: gum...@li... [mailto:gum...@li...] On Behalf Of Craig = Hughes Sent: Friday, February 11, 2005 9:22 PM To: gum...@li... Subject: Re: [Gumstix-users] Windows tool chain.... =20 On Feb 11, 2005, at 9:07 PM, Ted Larson wrote: =20 > So, I have been trying to get the tool chain to build under Cygwin,=20 > without much luck. Can anyone offer any ideas how to build the tool=20 > chain under Windows? Having to use a Linux box just so I can compile=20 > code for my gumstix seems excessive. =20 Of course, some people would say that having to pay $300 for an=20 operating system in order to use your desktop seems a little excessive=20 :) =20 But you should be able to get things working under cygwin, if you=20 install the various tools that the buildroot needs. What's breaking? =20 C =20 =20 =20 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id=14396&op=3Dick _______________________________________________ gumstix-users mailing list gum...@li... https://lists.sourceforge.net/lists/listinfo/gumstix-users =20 |
From: Craig H. <cr...@hu...> - 2005-02-12 19:37:21
|
On Feb 12, 2005, at 10:38 AM, Ted Larson wrote: > patches/patchin.sh: 43: Syntax error: "(" unexpected Hmm. That line is: function find_lines () { which looks syntactically fine... What is your /bin/sh in cygwin? Does it want function definitions to look some other way? C |
From: Ted L. <te...@la...> - 2005-02-14 18:10:44
|
It looks like it is using ash as it's /bin/sh, and ash definitely doesn't handle functions like this. I switched over to using bash instead and it goes much further..i.e. no more errors, but now I am running into trouble with cygwin hanging middle of the build from the sheer volume of shell forks. It will hang at places like "exiting directory xxx". Has anyone out there actually built the tool chain under cygwin? Is there some better way to get a tool chain running under windows? Thanks, - Ted -----Original Message----- From: gum...@li... [mailto:gum...@li...] On Behalf Of Craig Hughes Sent: Saturday, February 12, 2005 11:37 AM To: gum...@li... Subject: Re: [Gumstix-users] Windows tool chain.... On Feb 12, 2005, at 10:38 AM, Ted Larson wrote: > patches/patchin.sh: 43: Syntax error: "(" unexpected Hmm. That line is: function find_lines () { which looks syntactically fine... What is your /bin/sh in cygwin? Does it want function definitions to look some other way? C ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ gumstix-users mailing list gum...@li... https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Craig H. <cr...@hu...> - 2005-02-14 18:17:48
|
The build uses -j3 by default -- comment out the line "JLEVEL=-j3" in the top-level makefile to reduce the number of processes substantially. C On Feb 14, 2005, at 10:10 AM, Ted Larson wrote: > > It looks like it is using ash as it's /bin/sh, and ash definitely > doesn't > handle functions like this. I switched over to using bash instead and > it > goes much further..i.e. no more errors, but now I am running into > trouble > with cygwin hanging middle of the build from the sheer volume of shell > forks. It will hang at places like "exiting directory xxx". > > Has anyone out there actually built the tool chain under cygwin? > > Is there some better way to get a tool chain running under windows? > > Thanks, > > - Ted > > > > -----Original Message----- > From: gum...@li... > [mailto:gum...@li...] On Behalf Of Craig > Hughes > Sent: Saturday, February 12, 2005 11:37 AM > To: gum...@li... > Subject: Re: [Gumstix-users] Windows tool chain.... > > On Feb 12, 2005, at 10:38 AM, Ted Larson wrote: > >> patches/patchin.sh: 43: Syntax error: "(" unexpected > > Hmm. That line is: > > function find_lines () { > > which looks syntactically fine... What is your /bin/sh in cygwin? > Does it want function definitions to look some other way? > > C > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real > users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real > users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Ted L. <te...@la...> - 2005-02-14 21:40:43
|
Commenting out the JLEVEL helped tons...I have gone the furthest so far after that change. Now I am getting a compiler error when building the the arm version of linux, that defies explanation. It makes no sense why this would be a syntax error, unless the lex in the compiler is just plain broken because of something else. Any ideas on this one? Thanks, - Ted touch /home/Ted/gumstix-buildroot/build_arm/staging_dir/include/linux/version.h make -C /home/Ted/gumstix-buildroot/build_arm/linux-2.6.10gum CROSS_COMPILE=/ho me/Ted/gumstix-buildroot/build_arm/staging_dir/bin/arm-linux-uclibc- ARCH=arm make[1]: Entering directory `/home/Ted/gumstix-buildroot/build_arm/linux-2.6.10g um' CHK include/linux/version.h HOSTCC scripts/basic/fixdep HOSTCC scripts/basic/split-include HOSTCC scripts/basic/docproc CC scripts/mod/empty.o HOSTCC scripts/mod/mk_elfconfig In file included from scripts/mod/mk_elfconfig.c:4: /home/Ted/gumstix-buildroot/build_arm/staging_dir/include/elf.h:33: error: syntax error before "typedef" scripts/mod/mk_elfconfig.c:6: error: syntax error before "int" make[3]: *** [scripts/mod/mk_elfconfig] Error 1 make[2]: *** [scripts/mod] Error 2 make[1]: *** [scripts] Error 2 make[1]: Leaving directory `/home/Ted/gumstix buildroot/build_arm/linux2.6.10gum' make: *** [/home/Ted/gumstix-buildroot/build_arm/linux-2.6.10gum/arch/arm/boot/c ompressed/vmlinux] Error 2 -----Original Message----- From: gum...@li... [mailto:gum...@li...] On Behalf Of Craig Hughes Sent: Monday, February 14, 2005 10:18 AM To: gum...@li... Subject: Re: [Gumstix-users] Windows tool chain.... The build uses -j3 by default -- comment out the line "JLEVEL=-j3" in the top-level makefile to reduce the number of processes substantially. C On Feb 14, 2005, at 10:10 AM, Ted Larson wrote: > > It looks like it is using ash as it's /bin/sh, and ash definitely > doesn't > handle functions like this. I switched over to using bash instead and > it > goes much further..i.e. no more errors, but now I am running into > trouble > with cygwin hanging middle of the build from the sheer volume of shell > forks. It will hang at places like "exiting directory xxx". > > Has anyone out there actually built the tool chain under cygwin? > > Is there some better way to get a tool chain running under windows? > > Thanks, > > - Ted > > > > -----Original Message----- > From: gum...@li... > [mailto:gum...@li...] On Behalf Of Craig > Hughes > Sent: Saturday, February 12, 2005 11:37 AM > To: gum...@li... > Subject: Re: [Gumstix-users] Windows tool chain.... > > On Feb 12, 2005, at 10:38 AM, Ted Larson wrote: > >> patches/patchin.sh: 43: Syntax error: "(" unexpected > > Hmm. That line is: > > function find_lines () { > > which looks syntactically fine... What is your /bin/sh in cygwin? > Does it want function definitions to look some other way? > > C > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real > users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real > users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ gumstix-users mailing list gum...@li... https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Craig H. <cr...@hu...> - 2005-02-14 21:58:14
|
On Feb 14, 2005, at 1:40 PM, Ted Larson wrote: > Commenting out the JLEVEL helped tons...I have gone the furthest so far > after that change. Now I am getting a compiler error when building > the the > arm version of linux, that defies explanation. > > It makes no sense why this would be a syntax error, unless the lex in > the > compiler is just plain broken because of something else. > > Any ideas on this one? Here, I'm going to guess "line endings". When you installed Cygwin, did you tell it to use windows end-of-line characters, or unix end-of-line characters? Whichever you used, try re-installing and switch, then see if it works. C |
From: Ted L. <te...@la...> - 2005-02-14 23:54:22
|
I would think that the build would have crapped out much sooner if this were the case. It built the whole cross compiler and everything before it stopped. It was a good 30 minutes into the build process before this error showed up. I did double check that my default text file type is Unix too. Any other ideas? Thanks, - Ted -----Original Message----- From: gum...@li... [mailto:gum...@li...] On Behalf Of Craig Hughes Sent: Monday, February 14, 2005 1:58 PM To: gum...@li... Subject: Re: [Gumstix-users] Windows tool chain.... On Feb 14, 2005, at 1:40 PM, Ted Larson wrote: > Commenting out the JLEVEL helped tons...I have gone the furthest so far > after that change. Now I am getting a compiler error when building > the the > arm version of linux, that defies explanation. > > It makes no sense why this would be a syntax error, unless the lex in > the > compiler is just plain broken because of something else. > > Any ideas on this one? Here, I'm going to guess "line endings". When you installed Cygwin, did you tell it to use windows end-of-line characters, or unix end-of-line characters? Whichever you used, try re-installing and switch, then see if it works. C ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ gumstix-users mailing list gum...@li... https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Dave H. <dhy...@gm...> - 2005-02-14 22:19:26
|
> Here, I'm going to guess "line endings". When you installed Cygwin, > did you tell it to use windows end-of-line characters, or unix > end-of-line characters? Whichever you used, try re-installing and > switch, then see if it works. I haven't tested this recently, but gcc definitely wants to be installed on a binary mount. The C-preprocessor used to care about line endings (pre 3.0) but they redid the entire pre-processor so that it doesn't care anymore. The specs file (one of the files used by gcc) MUST have linux style line endings to work properly. Re-installing cygwin shouldn't really be necessary, just make sure that your mounts are binary. The choice that you make during the install just sets the default mount. You can always unmount and remount to change a mount from text to binary. My mounts look something like this: c:\MyDocuments on /MyDocuments type system (textmode) c:\cygwin\bin on /usr/bin type system (binmode) c:\cygwin\lib on /usr/lib type system (binmode) c:\cygwin on / type system (binmode) so if on my machine I wouldn't want to try building the toolchain from under /MyDocuments, but stuff under /gumstix would be fine (since / is mounted in binmode). -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: Dave H. <dhy...@gm...> - 2005-02-14 22:25:48
|
Oh yeah - if you try to build the netfilter portion of linux on a windows box, you'll run into some troubles. netfilter has some files like this: linux-2.6.10/include/linux/netfilter_ipv4/ipt_TCPMSS.h linux-2.6.10/include/linux/netfilter_ipv4/ipt_tcpmss.h On a linux system, these files are different files. However, on a windows system, when you expand the tarball, these will expand into the same file (because they only differ by case), and you'll only wind up with one of them being present. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: Ted L. <te...@la...> - 2005-02-14 23:51:05
|
Dave, This is what my mounts look like: Ted@Lion /home/ted $ mount C:\cygwin\bin on /usr/bin type system (binmode) C:\cygwin\lib on /usr/lib type system (binmode) C:\cygwin on / type system (binmode) c: on /cygdrive/c type user (binmode,noumount) d: on /cygdrive/d type user (binmode,noumount) e: on /cygdrive/e type user (binmode,noumount) m: on /cygdrive/m type user (binmode,noumount) t: on /cygdrive/t type user (binmode,noumount) v: on /cygdrive/v type user (binmode,noumount) x: on /cygdrive/x type user (binmode,noumount) y: on /cygdrive/y type user (binmode,noumount) Ted@Lion /home/ted $ I have been trying to build all the stuff in /home/ted/gumstix-buildroot So, since it is all under the / filesystem, it should all be in binmode I would think. Does this seem right? Since you are a cygwin user also, have you been able to get it to build under cygwin? - Ted -----Original Message----- From: gum...@li... [mailto:gum...@li...] On Behalf Of Dave Hylands Sent: Monday, February 14, 2005 2:19 PM To: gum...@li... Subject: Re: [Gumstix-users] Windows tool chain.... > Here, I'm going to guess "line endings". When you installed Cygwin, > did you tell it to use windows end-of-line characters, or unix > end-of-line characters? Whichever you used, try re-installing and > switch, then see if it works. I haven't tested this recently, but gcc definitely wants to be installed on a binary mount. The C-preprocessor used to care about line endings (pre 3.0) but they redid the entire pre-processor so that it doesn't care anymore. The specs file (one of the files used by gcc) MUST have linux style line endings to work properly. Re-installing cygwin shouldn't really be necessary, just make sure that your mounts are binary. The choice that you make during the install just sets the default mount. You can always unmount and remount to change a mount from text to binary. My mounts look something like this: c:\MyDocuments on /MyDocuments type system (textmode) c:\cygwin\bin on /usr/bin type system (binmode) c:\cygwin\lib on /usr/lib type system (binmode) c:\cygwin on / type system (binmode) so if on my machine I wouldn't want to try building the toolchain from under /MyDocuments, but stuff under /gumstix would be fine (since / is mounted in binmode). -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ gumstix-users mailing list gum...@li... https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Dave H. <dhy...@gm...> - 2005-02-15 01:45:30
|
Hi Ted, Your mounts look good. > I have been trying to build all the stuff in /home/ted/gumstix-buildroot > So, since it is all under the / filesystem, it should all be in binmode I > would think. Does this seem right? Yep. > Since you are a cygwin user also, have you been able to get it to build > under cygwin? I haven't tried building the gumstix environment specifically. I have built cross compilers under cygwin and I was able to get most of the WRT54G (Linksys 802.11g WiFi router) environment working under cygwin (it's a MIPS processor though and it was 2.4 not 2.6). glibc (which isn't being used on the gumstix) has some build issues under cygwin and netfilter has some build issues under cygwin. Sometimes, it takes getting just the right versions of tools. I guess I should try to build the gumstix. It's just that building under linux is WAY faster than building under cygwin, so my incentive to build under cygwin isn't there yet. To debug your particular problem, I'd find out the exact command line being used, and then produce a preprocessed output, so I could figure out why the compile error is happening. I noticed that it's doing a HOSTCC, so it seems like it's building some support piece that may require some headers or other package that isn't installed in cygwin. Sorry I can't be of much more help right now. Hmmm. I looked at elf.h line 33, and the __BEGIN_DECLS rings a bell. I can't remember what I did to fix it, but i remember that I had to do something. I'll see if I made any notes anywhere. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: Darren G. <ts...@ya...> - 2005-02-15 00:26:37
|
Hmmm... this is a shot-in-the-dark since I haven't tried to build under cygwin... The error is on the first line after the #include: > #include <stdint.h> > > /* Type for a 16-bit quantity. */ > typedef uint16_t Elf32_Half; Are these missing/broken: toolchain_build_arm/uClibc-0.9.27/include/stdint.h toolchain_build_arm/uClibc/include/stdint.h toolchain_build_arm/uClibc_dev/usr/include/stdint.h On Feb 14, 2005, at 1:40 PM, Ted Larson wrote: > Commenting out the JLEVEL helped tons...I have gone the furthest so far > after that change. Now I am getting a compiler error when building > the the > arm version of linux, that defies explanation. > > It makes no sense why this would be a syntax error, unless the lex in > the > compiler is just plain broken because of something else. > > Any ideas on this one? > > Thanks, > > - Ted > > > > touch > /home/Ted/gumstix-buildroot/build_arm/staging_dir/include/linux/ > version.h > make -C /home/Ted/gumstix-buildroot/build_arm/linux-2.6.10gum > CROSS_COMPILE=/ho > me/Ted/gumstix-buildroot/build_arm/staging_dir/bin/arm-linux-uclibc- > ARCH=arm > make[1]: Entering directory > `/home/Ted/gumstix-buildroot/build_arm/linux-2.6.10g > um' > CHK include/linux/version.h > HOSTCC scripts/basic/fixdep > HOSTCC scripts/basic/split-include > HOSTCC scripts/basic/docproc > CC scripts/mod/empty.o > HOSTCC scripts/mod/mk_elfconfig > In file included from scripts/mod/mk_elfconfig.c:4: > /home/Ted/gumstix-buildroot/build_arm/staging_dir/include/elf.h:33: > error: > syntax error before "typedef" > scripts/mod/mk_elfconfig.c:6: error: syntax error before "int" > make[3]: *** [scripts/mod/mk_elfconfig] Error 1 > make[2]: *** [scripts/mod] Error 2 > make[1]: *** [scripts] Error 2 > make[1]: Leaving directory `/home/Ted/gumstix > buildroot/build_arm/linux2.6.10gum' > make: *** > [/home/Ted/gumstix-buildroot/build_arm/linux-2.6.10gum/arch/arm/boot/c > ompressed/vmlinux] Error 2 > > -----Original Message----- > From: gum...@li... > [mailto:gum...@li...] On Behalf Of Craig > Hughes > Sent: Monday, February 14, 2005 10:18 AM > To: gum...@li... > Subject: Re: [Gumstix-users] Windows tool chain.... > > The build uses -j3 by default -- comment out the line "JLEVEL=-j3" in > the top-level makefile to reduce the number of processes substantially. > > C > > On Feb 14, 2005, at 10:10 AM, Ted Larson wrote: > >> >> It looks like it is using ash as it's /bin/sh, and ash definitely >> doesn't >> handle functions like this. I switched over to using bash instead and >> it >> goes much further..i.e. no more errors, but now I am running into >> trouble >> with cygwin hanging middle of the build from the sheer volume of shell >> forks. It will hang at places like "exiting directory xxx". >> >> Has anyone out there actually built the tool chain under cygwin? >> >> Is there some better way to get a tool chain running under windows? >> >> Thanks, >> >> - Ted >> >> >> >> -----Original Message----- >> From: gum...@li... >> [mailto:gum...@li...] On Behalf Of Craig >> Hughes >> Sent: Saturday, February 12, 2005 11:37 AM >> To: gum...@li... >> Subject: Re: [Gumstix-users] Windows tool chain.... >> >> On Feb 12, 2005, at 10:38 AM, Ted Larson wrote: >> >>> patches/patchin.sh: 43: Syntax error: "(" unexpected >> >> Hmm. That line is: >> >> function find_lines () { >> >> which looks syntactically fine... What is your /bin/sh in cygwin? >> Does it want function definitions to look some other way? >> >> C >> >> >> >> ------------------------------------------------------- >> SF email is sponsored by - The IT Product Guide >> Read honest & candid reviews on hundreds of IT Products from real >> users. >> Discover which products truly live up to the hype. Start reading now. >> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> >> >> >> >> ------------------------------------------------------- >> SF email is sponsored by - The IT Product Guide >> Read honest & candid reviews on hundreds of IT Products from real >> users. >> Discover which products truly live up to the hype. Start reading now. >> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real > users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real > users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Christopher Vo <chr...@gm...> - 2005-02-15 05:03:10
|
I did a test build of the toolchain on Cygwin myself and it crapped out at precisely the same place as Ted's did with the elf.h nonsense. Like Dave mentioned, the preprocessor directive __BEGIN_DECLS Darren Gibbs wrote: > Hmmm... this is a shot-in-the-dark since I haven't tried to build > under cygwin... The error is on the first line after the #include: > >> #include <stdint.h> >> >> /* Type for a 16-bit quantity. */ >> typedef uint16_t Elf32_Half; > > > Are these missing/broken: > > toolchain_build_arm/uClibc-0.9.27/include/stdint.h > toolchain_build_arm/uClibc/include/stdint.h > toolchain_build_arm/uClibc_dev/usr/include/stdint.h > > > On Feb 14, 2005, at 1:40 PM, Ted Larson wrote: > >> Commenting out the JLEVEL helped tons...I have gone the furthest so far >> after that change. Now I am getting a compiler error when building >> the the >> arm version of linux, that defies explanation. >> >> It makes no sense why this would be a syntax error, unless the lex >> in the >> compiler is just plain broken because of something else. >> >> Any ideas on this one? >> >> Thanks, >> >> - Ted >> >> >> >> touch >> /home/Ted/gumstix-buildroot/build_arm/staging_dir/include/linux/ >> version.h >> make -C /home/Ted/gumstix-buildroot/build_arm/linux-2.6.10gum >> CROSS_COMPILE=/ho >> me/Ted/gumstix-buildroot/build_arm/staging_dir/bin/arm-linux-uclibc- >> ARCH=arm >> make[1]: Entering directory >> `/home/Ted/gumstix-buildroot/build_arm/linux-2.6.10g >> um' >> CHK include/linux/version.h >> HOSTCC scripts/basic/fixdep >> HOSTCC scripts/basic/split-include >> HOSTCC scripts/basic/docproc >> CC scripts/mod/empty.o >> HOSTCC scripts/mod/mk_elfconfig >> In file included from scripts/mod/mk_elfconfig.c:4: >> /home/Ted/gumstix-buildroot/build_arm/staging_dir/include/elf.h:33: >> error: >> syntax error before "typedef" >> scripts/mod/mk_elfconfig.c:6: error: syntax error before "int" >> make[3]: *** [scripts/mod/mk_elfconfig] Error 1 >> make[2]: *** [scripts/mod] Error 2 >> make[1]: *** [scripts] Error 2 >> make[1]: Leaving directory `/home/Ted/gumstix >> buildroot/build_arm/linux2.6.10gum' >> make: *** >> [/home/Ted/gumstix-buildroot/build_arm/linux-2.6.10gum/arch/arm/boot/c >> ompressed/vmlinux] Error 2 >> >> -----Original Message----- >> From: gum...@li... >> [mailto:gum...@li...] On Behalf Of >> Craig Hughes >> Sent: Monday, February 14, 2005 10:18 AM >> To: gum...@li... >> Subject: Re: [Gumstix-users] Windows tool chain.... >> >> The build uses -j3 by default -- comment out the line "JLEVEL=-j3" in >> the top-level makefile to reduce the number of processes substantially. >> >> C >> >> On Feb 14, 2005, at 10:10 AM, Ted Larson wrote: >> >>> >>> It looks like it is using ash as it's /bin/sh, and ash definitely >>> doesn't >>> handle functions like this. I switched over to using bash instead and >>> it >>> goes much further..i.e. no more errors, but now I am running into >>> trouble >>> with cygwin hanging middle of the build from the sheer volume of shell >>> forks. It will hang at places like "exiting directory xxx". >>> >>> Has anyone out there actually built the tool chain under cygwin? >>> >>> Is there some better way to get a tool chain running under windows? >>> >>> Thanks, >>> >>> - Ted >>> >>> >>> >>> -----Original Message----- >>> From: gum...@li... >>> [mailto:gum...@li...] On Behalf Of Craig >>> Hughes >>> Sent: Saturday, February 12, 2005 11:37 AM >>> To: gum...@li... >>> Subject: Re: [Gumstix-users] Windows tool chain.... >>> >>> On Feb 12, 2005, at 10:38 AM, Ted Larson wrote: >>> >>>> patches/patchin.sh: 43: Syntax error: "(" unexpected >>> >>> >>> Hmm. That line is: >>> >>> function find_lines () { >>> >>> which looks syntactically fine... What is your /bin/sh in cygwin? >>> Does it want function definitions to look some other way? >>> >>> C >>> >>> >>> >>> ------------------------------------------------------- >>> SF email is sponsored by - The IT Product Guide >>> Read honest & candid reviews on hundreds of IT Products from real >>> users. >>> Discover which products truly live up to the hype. Start reading now. >>> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >>> _______________________________________________ >>> gumstix-users mailing list >>> gum...@li... >>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>> >>> >>> >>> >>> >>> ------------------------------------------------------- >>> SF email is sponsored by - The IT Product Guide >>> Read honest & candid reviews on hundreds of IT Products from real >>> users. >>> Discover which products truly live up to the hype. Start reading now. >>> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >>> _______________________________________________ >>> gumstix-users mailing list >>> gum...@li... >>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> >> >> >> ------------------------------------------------------- >> SF email is sponsored by - The IT Product Guide >> Read honest & candid reviews on hundreds of IT Products from real >> users. >> Discover which products truly live up to the hype. Start reading now. >> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> >> >> >> >> ------------------------------------------------------- >> SF email is sponsored by - The IT Product Guide >> Read honest & candid reviews on hundreds of IT Products from real >> users. >> Discover which products truly live up to the hype. Start reading now. >> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Dave H. <dhy...@gm...> - 2005-02-15 13:36:20
|
Hmm. This is for Craig. I upgraded to the latest cygwin, downloaded the latest gumstix source and ran into some troubles during the linux build (the make of silentoldconfig). The original 2.6.10 Makefile has this: HOSTCFLAGS = -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer and the one I see looks like this: HOSTCFLAGS = -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -idirafter "`$(CC) -print-file-name=include`/../../../../../include/" Unfortunately, if you're starting from scratch, buildroot needs to build the config in order to build the toolchain, but it would now appear that the config now needs the toolchain. Catch-22. This problem seems to have been introduced in 999-gumstix-kernel-osx.patch. Suprisingly, the make still seemed to work. I also ran into what appears to be a typo in the linux.mk file. There is a reference to linux-depmod.patchi, which I assume is supposed to be linux-depmod.patch (without the trailing i. My attempt at building the toolchain failed: make[1]: Entering directory `/gumstix/gumstix-buildroot/toolchain_build_arm/uClibc-0.9.27' make CROSS=/gumstix/gumstix-buildroot/build_arm/staging_dir/bin/arm-linux-uclibc- CC=/gumstix/gumstix-buildroot/build_arm/staging_dir/bin/arm-linux-uclibc-gcc - C utils make[2]: Entering directory `/gumstix/gumstix-buildroot/toolchain_build_arm/uClibc-0.9.27/utils' /gumstix/gumstix-buildroot/build_arm/staging_dir/bin/arm-linux-uclibc-gcc -Wall -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fstrict-aliasing -Os -funit-at-a-time -mlittle-endian -mtune=xscale -march=armv5te -Wa,-mcpu=xscale -fno-builtin -nostdinc -D_LIBC -I../include -I. -isystem /gumstix/gumstix-bui ldroot/build_arm/staging_dir/lib/gcc/arm-linux-uclibc/3.4.2/include -DNDEBUG -fPIC -Wl,-s \ -DUCLIBC_RUNTIME_PREFIX=\"/\" \ -DUCLIBC_LDSO=ld-uClibc.so.0 -I. -I../ldso/include \ ldd.c -o ldd collect2: ld terminated with signal 11 [Segmentation fault], core dumped make[2]: *** [ldd] Error 1 make[2]: Leaving directory `/gumstix/gumstix-buildroot/toolchain_build_arm/uClibc-0.9.27/utils' make[1]: *** [utils] Error 2 make[1]: Leaving directory `/gumstix/gumstix-buildroot/toolchain_build_arm/uClibc-0.9.27' make: *** [/gumstix/gumstix-buildroot/build_arm/root/usr/bin/ldd] Error 2 So obviously the latest cygwin has problems (my gcc reports 3.3.3, ld is 2.15.94) -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: Craig H. <cr...@hu...> - 2005-02-15 18:00:44
|
On Feb 15, 2005, at 5:36 AM, Dave Hylands wrote: > HOSTCFLAGS = -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer > -idirafter "`$(CC) -print-file-name=include`/../../../../../include/" > > Unfortunately, if you're starting from scratch, buildroot needs to > build the config in order to build the toolchain, but it would now > appear that the config now needs the toolchain. Catch-22. No -- that $(CC) is host CC, not cross CC. You definitely need to have a host compiler set up before you get underway with the buildroot. This is fine, and is there because OSX's gcc doesn't include the right include directories by default or something. > I also ran into what appears to be a typo in the linux.mk file. There > is a reference to linux-depmod.patchi, which I assume is supposed to > be linux-depmod.patch (without the trailing i. Stupid vi, requiring you to type printable characters to switch modes.... I'll fix that -- could well be why things haven't been working for folks compiling on machines which don't have mod-utils 2.6+ installed. C |
From: Dave H. <dhy...@gm...> - 2005-02-15 19:23:14
|
Hi Craig, > No -- that $(CC) is host CC, not cross CC. You definitely need to have > a host compiler set up before you get underway with the buildroot. > This is fine, and is there because OSX's gcc doesn't include the right > include directories by default or something. I'm confused. Make uses lazy evaluation, so later one when this assignment occurs: CC = $(CROSS_COMPILE)gcc This is what will get used in HOSTCCFLAGS This is backed up by running make V=1, and seeing this echoed: gcc -Wp,-MD,scripts/basic/.fixdep.d -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -idirafter "`/usr2/gumstix/gumstix-buildroot/build_arm/staging_dir/bin/arm-linux-uclibc-gcc -print-file-name=include`/../../../../../include/" -o scripts/basic/fixdep scripts/basic/fixdep.c CC got expanded to /...path.../arm-linux-uclibc-gcc -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |