From: Shawn Starr <Shawn.Starr@Home.net>
To: Jes Sorensen <jes@linuxcare.com>, linux-kernel@vger.kernel.org
Subject: Re: Compiling 2.4.1-preX series - Confirmed - PGCC sucks
Date: Wed, 17 Jan 2001 14:08:42 -0500 [thread overview]
Message-ID: <3A65EDB9.722C06A1@Home.net> (raw)
In-Reply-To: <3A64F6E0.778F5734@Home.net> <d3bst6kjml.fsf@lxplus015.cern.ch> <3A650198.8523D94F@Home.net>
Yes, it appears the PGCC patches *BREAK* GCC (go figure). 2.4.1-pre7 compiled
fine. JUST as pre8 was released *sigh*
oh well, at least now I wont have to worry about any compiler bugs (unless
some are discovered with 2.95.2) ;)
Shawn.
Shawn Starr wrote:
> Fair enough, but something in bugs.h changed from 2.4.0 to 2.4.1-preX and
> broke my GCC, I shall recompile GCC with no PGCC patches however if this
> happens still then there's a problem somewhere.
>
> I dont know what FXSR is but there was no problem in 2.4.0 with this.
>
> diff include/asm-i386/bugs.h ../linux/include/asm-i386/bugs.h |
> more78a79
> > #if defined(CONFIG_X86_FXSR) || defined(CONFIG_X86_RUNTIME_FXSR)
> 82,85c83,85
> < if (offsetof(struct task_struct, thread.i387.fxsave) & 15) {
> < extern void __buggy_fxsr_alignment(void);
> < __buggy_fxsr_alignment();
> < }
> ---
> > if (offsetof(struct task_struct, thread.i387.fxsave) & 15)
> > panic("Kernel compiled for PII/PIII+ with FXSR, data not 16-byte
> aligned!");
> >
> 90a91,92
>
> Jes Sorensen wrote:
>
> > >>>>> "Shawn" == Shawn Starr <Shawn.Starr@Home.net> writes:
> >
> > Shawn> Which compiler will compile the 2.4.1-preX series? Since 2.4.0,
> > Shawn> my GCC 2.95.2 patched with PGCC 2.95.3 (which creates
> > Shawn> pgcc-2.95.2) refuses to compile any versions after this. Which
> > Shawn> is the next stable and binary compatable compiler?
> >
> > Shawn> Anyone have any suggestions? I dont wish to use the development
> > Shawn> GCC 2.96/2.97 because they will break my binary compatability
> > Shawn> with pgcc-2.95.2/3.
> >
> > Yes, it's simple you want the real gcc 2.96/2.97 or egcs-1.1.2. pgcc
> > is not supported.
> >
> > Jes
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2001-01-17 19:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-17 1:35 Compiling 2.4.1-preX series Shawn Starr
2001-01-17 2:17 ` Jes Sorensen
2001-01-17 2:21 ` Shawn Starr
2001-01-17 19:08 ` Shawn Starr [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=3A65EDB9.722C06A1@Home.net \
--to=shawn.starr@home.net \
--cc=jes@linuxcare.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox