Date: Sat, 07 May 2011 09:13:38 +0300 From: Georgi Geshev <root@...k-labs.exploits-bg.com> To: owl-dev@...ts.openwall.com Subject: Re: gcc update -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 5/6/2011 9:26 PM, Solar Designer wrote: > Hi Georgi, > > On Fri, May 06, 2011 at 03:32:14AM +0300, Georgi Geshev wrote: >> I've built the GCC 4.6.0 (no patches applied), GMP 4.3.2 (appropriate >> Fedora patches applied), MPFR 3.0.1 (no patches applied) and MPC 0.9 (no >> patches applied) packages, though I still need to clean up and improve >> the spec files. > > Great. Please post your spec files in here - as they are, before you > spend any more time on them. I'd like to take a look, and others might > provide helpful comments as well. > >> Here's the list of packages that initially failed to build with the new >> compiler toolchain - >> >> cpio >> elfutils-libelf >> flex >> glibc >> kernel >> libtool >> mdadm >> perl >> shadow-utils >> util-linux >> vim >> >> I'll do my best to further resolve the build issues. > > Before you do, please post excerpts from build logs showing just how > these packages failed to build. I'm also attaching a handy bzipped archive of the error log files. > > For others in here - Georgi only did this test on i686 so far (not > x86_64 yet). (That's fine, I merely want it mentioned.) > > Thanks, > > Alexander > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (MingW32) iQEcBAEBAgAGBQJNxOMQAAoJECp4GRJNSNT55DsIALHMStwQp8Q4AUU82PJILmdY ZxIVIlnGjsbyHOSe+4U3pmW2cP8d9sh7Tb2d7CcawSCccpFe/gj8unyO0g5XKm3W 8nsPm9t4Ya0XVBmqCb/pOOdRmY2lrBSyMJVUoxPGXd0YcoInnBa9Bzq6CAK7ml+5 KjN5NsxsKzfAKsECCFGSsbYuoGCsZzyTMlciRFGZ06P7EiYt6SbkUwn4k88kzGta 91hrF85i/xLJbCU6Wr/aQrRFHkeKidP3X2UpOGebE9WlA3eegBo+G0DtagNMFZwz XtVJ7tPj5Wg4MAo4rKFpBbyuy0stVOkGj/3ASIPVNScPF1m1CmHiPgWn71abEkk= =p2Xv -----END PGP SIGNATURE----- Download attachment "build-errors.bz2" of type "application/octet-stream" (2512 bytes)
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.