> -----Original Message----- > From: [email protected] [mailto:ptxdist- > [email protected]] On Behalf Of Michael Olbrich > Sent: Sunday, March 13, 2011 10:20 AM > To: [email protected] > Subject: Re: [ptxdist] Build problem with OSELAS.Toolchain-2011.02.0 > > Hi, > > On Wed, Mar 09, 2011 at 12:54:12PM +0100, Juergen Beisert wrote: > > David Lightstone wrote: > > > (2) I observe zlib-1.2.5 to be present in directory build-host. > > > Quite possibly it is intended as the non-hack solution. (if so, > > > should it be in the include path?). It certainly contains zlib.h. > > > Should it be in the include file path somewhere? > > > > Hmm, as the toolchain should run later on on your host, using the > > local zlib might not be a good idea. But currently I also do not know, > > why the zlib is required. > > The situation is a bit complicated. In theory the gcc sources come with a zlib that > can be used. Unfortunately for gcc-4.5 using it breaks building with some > configure options. It's not easy to fix and upstream is in no hurry. > To work around this issue I added the host-zlib package and "--with-system-zlib". > The zlib is built statically, so no problems using the toolchain on the host system. > > I guess detecting this zlib is broken. Can someone send me the relevant sections > from the logfile?
Tell me what you need, I can re-create the phenomena (made many builds since observing the phenomena) What do you mean by breaks building with some configure options? The starting point for the inquiry was a failure to compile lto-compress.c I did not have the development files for zlib installed on the HOST computer Initially I just hacked into the configuration for the gcc make, and removed the "--with-system-zlib". The initial suggestion was to install the zlib development files on the host, so I did, and the compile proceeded successfully. I subsequently wondered whether about which library would be used at link time. The one from the host, targeted to the host, or the one from the target (1) To me this meant that the bootstrap compiler had to be used (with the bootstrap configured to build zlib using the GCC version of zilb) (2) The bootstrap would have to be used to build the preferred target version of zlib (3) The target version of zlib and the bootstrap would have to be used to build the final GCC Is this consistent with the intended preparation of a cross compiler? dbl > > Michael > > -- > Pengutronix e.K. | | > Industrial Linux Solutions | http://www.pengutronix.de/ | > Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | > Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | > > -- > ptxdist mailing list > [email protected] -- ptxdist mailing list [email protected]
