All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Pfeiffer <roto@gmx.net>
To: Russell Coker <russell@coker.com.au>, SE-Linux <selinux@tycho.nsa.gov>
Subject: Re: gcc-2.95: checking for va_list assignment copy... configure: error: no
Date: Tue, 03 Aug 2004 13:12:48 +0200	[thread overview]
Message-ID: <1091531568.1291.78.camel@debby> (raw)
In-Reply-To: <200408022013.51748.russell@coker.com.au>

On Mon, 2004-08-02 at 12:13, Russell Coker wrote:
> On Mon, 2 Aug 2004 20:04, Wolfgang Pfeiffer <roto@gmx.net> wrote:
> > > Why not just use the latest GCC?
> >
> > Because I thought it's a good idea to compile the SE-packages with the
> > same gcc version as the one I will use to compile the kernel.
> 
> That's not necessary.  

Good to know ... :)

> Using a different version of GCC for the kernel 
> shouldn't be a big deal (think of kgcc).
> 
> > And as, IINM, at least for Intel machines (I'm running ppc) gcc 2.95.3
> > still seems to be the recommended version to compile 2.6 kernels I'm
> > using 2.95 for compiling other packages, too ..
> 
> gcc 3.3.4 is working well for me when I compile my i386 kernels.

Good news for me. Thanks for letting me know

> 
> > Compiler issues.
> > ~~~~~~~~~~~~~~~~
> > - The recommended compiler (for x86) is still 2.95.3.
> > - When compiled with a modern gcc (Ie gcc 3.x), 2.6 will use additional
> >   optimisations that 2.4 didn't. This may shake out compiler bugs that
> >   2.4 didn't expose.
> > - Do not use gcc 3.0.x on x86 due to a stack pointer handling bug.
> > - gcc 2.96 is not supported with CONFIG_FRAME_POINTER=y due to a stack
> >   pointer handling bug.
> > ----------------------------------------------------
> >
> > I'll be happily using gcc-3.4 (this is the latest reliable gcc version:
> > Is this correct?) for packages and kernels  if someone tells me that
> > nowadays this is as safe as 2.95.
> 
> 3.3.4 works well for me.  I haven't tried 3.4 yet, but I will probably do so 
> soon.

I'll probably try 3.4, but at least 3.3, for the packages and the 2.6
kernel ... but not being quite sure on gcc-3.4 yet.

So the next steps will be building the packages, and then let's hope I
could manage to find a place to offer them ... :)

Thanks again

Regards
Wolfgang
-- 
Profile, links: http://profiles.yahoo.com/wolfgangpfeiffer


--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

      reply	other threads:[~2004-08-03 11:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-01 17:58 gcc-2.95: checking for va_list assignment copy... configure: error: no Wolfgang Pfeiffer
2004-08-02  8:10 ` Russell Coker
2004-08-02 10:04   ` Wolfgang Pfeiffer
2004-08-02 10:13     ` Russell Coker
2004-08-03 11:12       ` Wolfgang Pfeiffer [this message]

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=1091531568.1291.78.camel@debby \
    --to=roto@gmx.net \
    --cc=russell@coker.com.au \
    --cc=selinux@tycho.nsa.gov \
    /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.