All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alexander E. Patrakov" <patrakov@ums.usu.ru>
To: linux-kernel@vger.kernel.org
Subject: Re: Recommended compiler version and NPTL
Date: Sun, 30 May 2004 09:52:07 +0600	[thread overview]
Message-ID: <40B95A67.3000807@ums.usu.ru> (raw)

There is one more place except the r8169 driver where gcc 2.95.3 is bad. 
To reproduce the problem:

(you will need HJL Binutils >= 2.14.90.0.8 and gcc 3.3.x)

Check out a known good glibc from CVS:

cvs -z 3 -d :pserver:anoncvs@sources.redhat.com:/cvs/glibc \
     export -d glibc-2.3.4-20040510 -D "14:45:00 2004-05-10 UTC" libc
sed -i -e "s/stable/2004-05-10/" -e "s/2\.3\.3/2.3.4/" \
     glibc-2.3.4-20040510/version.h

Alternatively, there is a tarball available (created with these 
instructions) which you can download from the following location: 
ftp://gaosu.rave.org/pub/linux/lfs/packages/conglomeration/glibc-2.3.4-20040510.tar.bz2

Build glibc:

cd glibc-2.3.4-20040510
mkdir ../glibc-build
cd ../glibc-build
../glibc-2.3.4-20040510/configure --prefix=/usr \
     --disable-profile --enable-add-ons=nptl --with-tls \
     --without-cvs \
     --with-headers=/usr/src/linux/include
make
(we will not install anything)

Back up the glibc-build directory for future reference, but don't remove 
it now.

Issue the "make ckeck" command when running linux-2.6.6 compiled with 
gcc 3.3.3. If you get a failure, make a note of it and reissue the "make 
check" command.

Once you know all failures, remove the glibc-build directory and restore 
it from the backup you made previously.

Reboot into linux-2.6.6 compiled with gcc-2.95.3 published by Free 
Software Foundation. Redo the tests. You will notice several additional 
errors in NPTL testsuite. That's why I think that linux-2.6.6 should 
never be compiled with gcc-2.95.3.

-- 
Alexander E. Patrakov
I am not subscribed to LKML, so please CC: me

                 reply	other threads:[~2004-05-30  3:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=40B95A67.3000807@ums.usu.ru \
    --to=patrakov@ums.usu.ru \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.