From: Mikael Pettersson <mikpe@it.uu.se>
To: Udo van den Heuvel <udovdh@xs4all.nl>
Cc: Mikael Pettersson <mikpe@it.uu.se>, linux-kernel@vger.kernel.org
Subject: Re: crypt issue with 2.6.30/gcc 4.4.0?
Date: Sun, 14 Jun 2009 17:39:42 +0200 [thread overview]
Message-ID: <18997.6590.427221.898997@pilspetsen.it.uu.se> (raw)
In-Reply-To: <4A35159E.7080004@xs4all.nl>
Udo van den Heuvel writes:
> On 06/14/2009 05:16 PM, Mikael Pettersson wrote:
> > Udo van den Heuvel writes:
> > > How can I find out what's the cause for the password issue?
> >
> > Instead of changing two variables at once (kernel version AND gcc version)
> > you keep one constant and vary the other.
> >
> > IOW, rebuild 2.6.29.4 with gcc-4.4 and test.
> > Then rebuild 2.6.30 with gcc-4.3 or older and test.
>
> I can do the 2.6.29.4 build with gcc-4.4 but the gcc-4.3 case is harder
> to do: I need to convince Fedora to install a 2nd compiler-version (and
> rest of toolchain).
Not true. Just as you can choose from multiple self-built kernels
you can build and choose dynamically from multiple self-built GCCs.
E.g., for this particular case, download gcc-4.3.3.tar.bz2, tar jxf it,
mkdir objdir, cd objdir, /path/to/gcc-4.3.3/configure --prefix=/tmp/gcc43
--enable-languages=c, make, make install, cd /path/to/linux-2.6.30,
PATH=/tmp/gcc43/bin:$PATH make, and so on.
next prev parent reply other threads:[~2009-06-14 15:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-14 13:37 crypt issue with 2.6.30/gcc 4.4.0? Udo van den Heuvel
2009-06-14 15:16 ` Mikael Pettersson
2009-06-14 15:22 ` Udo van den Heuvel
2009-06-14 15:39 ` Mikael Pettersson [this message]
2009-06-14 15:36 ` Udo van den Heuvel
2009-06-14 15:54 ` Milan Broz
2009-06-14 16:10 ` Udo van den Heuvel
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=18997.6590.427221.898997@pilspetsen.it.uu.se \
--to=mikpe@it.uu.se \
--cc=linux-kernel@vger.kernel.org \
--cc=udovdh@xs4all.nl \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox