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: > > > Hi, > > > > > > I have just been working on "Bering-uClibc 4.x - Developer Guide" in > > > the Wiki at > > > https://sourceforge.net/apps/mediawiki/leaf/index.php?title=Bering-uCli > > > bc_4 .x_-_Developer_Guide > > > > > > A couple of the pages are direct imports of the "buildtool" and > > > "buildpacket" chapters from the existing Developer Guide, not yet > > > amended for 4.x. > > > > > > Comments? > > > > Hi; > > > > unfortunately the buildenv is yet not self-contained, so we do need a few > > packages on the build host. An additional page mentining prerequisites > > wouldbe helpful. Amongst others "texinfo" and "asciidoc" comes to mind. > > The first is to let the developer build buildenv (binutils), the latter > > to build tinyproxy. > > Agree that we should list these. I had this sort of content in mind for > http://sourceforge.net/apps/mediawiki/leaf/index.php?title=Bering-uClibc_4. > x_-_Developer_Guide_-_Preparing_the_Build_Environment Have just added an > initial list to that page.
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. We shouldn't mix packages needed on the build host and packages that are needed to compile a special source but provided by buildenv. E.g. I added m4 and gawk, which are necessary for various packages, but _not_ in our buildenv - so we have to use those on the host for the time being. kp ------------------------------------------------------------------------------ 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
