From: Thomas Steudten <alpha@steudten.com>
To: linux-admin@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-alpha@vger.kernel.org
Subject: Kernel crash/ oops >= 2.6.5 with gcc 3.4.0 on alpha
Date: Fri, 28 May 2004 13:47:12 +0200 [thread overview]
Message-ID: <40B726C0.5030400@steudten.com> (raw)
Hi
Sorry, maybe I miss some message before.
I build the 2.6.6 kernel with gcc-3.4.0 and it crashs after
start some init scripts (got no log at this time).
So I tried to rebuild my last build 2.6.5, and this
crashs to. The build with gcc-3.3.3 works without problems.
modutils-2.4.27
http://www.uwsg.iu.edu/hypermail/linux/kernel/0405.1/1532.html
No other application seems to fail with gcc-3.4.0 so I think
this problem is in context to the relocation, modules and gcc-3.4.0.
make modules
make[1]: `arch/alpha/kernel/asm-offsets.s' is up to date.
CC [M] fs/binfmt_em86.o
{standard input}: Assembler messages:
{standard input}:7: Warning: setting incorrect section attributes for .got
CC [M] fs/quota_v2.o
{standard input}: Assembler messages:
{standard input}:7: Warning: setting incorrect section attributes for .got
CC [M] fs/autofs/dirhash.o
CC [M] fs/autofs/init.o
{standard input}: Assembler messages:
{standard input}:7: Warning: setting incorrect section attributes for .got
CC [M] fs/autofs/inode.o
On x86 everything works without problems.
Please CC me.
--
Tom
LINUX user since kernel 0.99.x 1994.
RPM Alpha packages at http://alpha.steudten.com/packages
Want to know what S.u.S.E 1995 cdrom-set contains?
next reply other threads:[~2004-05-28 11:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-28 11:47 Thomas Steudten [this message]
2004-05-28 12:37 ` Kernel crash/ oops >= 2.6.5 with gcc 3.4.0 on alpha Herbert Poetzl
2004-05-28 14:06 ` Thomas Steudten
2004-05-28 21:19 ` Balint Cristian
2004-05-28 15:16 ` Ivan Kokshaysky
2004-05-28 13:46 ` mikado
2004-05-28 14:04 ` Ivan Kokshaysky
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=40B726C0.5030400@steudten.com \
--to=alpha@steudten.com \
--cc=linux-admin@vger.kernel.org \
--cc=linux-alpha@vger.kernel.org \
--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.