On Tue, 2010-09-21 at 19:24 +0100, davidMbrooke wrote:
> On Tue, 2010-09-21 at 19:09 +0200, KP Kirchdoerfer wrote:
> > Am Dienstag, 21. September 2010, 11:22:49 schrieb davidMbrooke:
> > > On Mon, 2010-09-20 at 23:13 +0200, KP Kirchdoerfer wrote:
> > > > Am Montag, 20. September 2010, 22:25:18 schrieb davidMbrooke:
> > David;
> >
> > are you shure that bison and flex are prerequisites on the build host?
> > Both are provided in the buildtool environment - and reading through the
> > mails it looks like your syslog-ng problem has been solved using flex from
> > buildenv.
>
> I thought so, but now I am not so sure...
> I will do some checking...
>
For the record, I have just been re-building my build environment on a
different machine (faster, running 64-bit Fedora 13). I did already have
flex installed in the host environment, but not bison. Trying to build
"iproute" failed with the following error:
/home/leaf/src/bering-uclibc4/buildtool/staging/bin/gcc-m32
-D_GNU_SOURCE -Os -march=i686 -Wstrict-prototypes -Wall -I../include
-DRESOLVE_HOSTNAMES -DLIBDIR=\"/usr/lib/\" -DCONFIG_GACT
-DCONFIG_GACT_PROB -c -o m_ematch.o m_ematch.c
bison -d -t -v -o emp_ematch.yacc.c emp_ematch.y
make[2]: bison: Command not found
make[2]: *** [emp_ematch.yacc.c] Error 127
make[2]: Leaving directory
`/home/leaf/src/bering-uclibc4/buildtool/source/iproute/iproute2-2.6.35/tc'
make[1]: *** [all] Error 2
Installing bison in the host environment fixed it, so we do need bison
installed. From the Makefile it looks like iproute needs flex too though
I did not de-install that to confirm.
davidMbrooke
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
leaf-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/leaf-devel
