Latest CVS download won't compile for me

[Thomas d'Otreppe]

I had once my program to compile fine under slackware and it wasn't
compiling on suse, spitting errors like this. I wondered why, because
the person had everything ok and other parts compiled fine.
It was the order of the #include that made this problem appearing.
Changing the order solved it.

Thomas

2006/9/23, Rob Landley <rob at landley.net>:
(...)
>
> Something's happening before that other header is included.  Some #define, or
> some other header getting #included, that's driving one of your standard
> system headers nuts.
>
> Possibly you want to do the make with V=2 so you can see what gcc invocations
> it's actually doing, and then run gcc -E to see what's coming out of the
> preprocessor?
>
> Rob


2006/9/23, Rob Landley <rob at landley.net>:
> On Friday 22 September 2006 3:07 pm, Ron Jobmann wrote:
> > This morning I grabbed the latest from CVS because there have been some
> > small changes and for my build system Busybox networking is still
> > broken. I've included the messages below. [Note: it appears the applets
> > and some of the other utils build fine]
> >
> > make[2]: Entering directory `trunk/user/busybox'
> > CC networking/route.o
> > In file included from /usr/local/arm-linux/sys-include/net/route.h:28,
> > from trunk/user/busybox/networking/route.c:32:
> > /usr/local/arm-linux/sys-include/net/dst.h:30: error: parse error before
> > "atomic_t"
> > /usr/local/arm-linux/sys-include/net/dst.h:61: error: parse error before
> > "tclassid"
>
> That's one of your system headers, not a part of BusyBox.  We may be
> triggering something, but I haven't seen this problem before.
>
> > I'm using:
> > [mymachine]$ arm-linux-gcc -v
> > Reading specs from /usr/local/lib/gcc-lib/arm-linux/3.3.2/specs
> > Configured with: ../configure --target=arm-linux --disable-shared
> > --with-headers=/home/gerg/new-wave.xscale/linux-2.4.x/include
> > --with-gnu-as --with-gnu-ld --enable-multilib
> > Thread model: posix
> > gcc version 3.3.2
> >
> > which builds everything else in the user apps tree, including Busybox
> > 1.0.0.
> >
> > Any suggestions or more info needed or?
>
> Something's happening before that other header is included.  Some #define, or
> some other header getting #included, that's driving one of your standard
> system headers nuts.
>
> Possibly you want to do the make with V=2 so you can see what gcc invocations
> it's actually doing, and then run gcc -E to see what's coming out of the
> preprocessor?
>
> Rob
> --
> Never bet against the cheap plastic solution.
> _______________________________________________
> busybox mailing list
> busybox at busybox.net
> http://busybox.net/cgi-bin/mailman/listinfo/busybox
>