From: "Thomas Bächler" <thomas@archlinux.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: "Thomas Bächler" <thomas@archlinux.org>,
"Ingo Molnar" <mingo@elte.hu>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.24-rc1-82798a1 compile failure (x86_64)
Date: Tue, 30 Oct 2007 10:10:40 +0100 [thread overview]
Message-ID: <4726F510.9060207@archlinux.org> (raw)
In-Reply-To: <alpine.LFD.0.9999.0710300033470.3186@localhost.localdomain>
Thomas Gleixner schrieb:
> On Tue, 30 Oct 2007, Thomas Bächler wrote:
>
>> Thomas Gleixner schrieb:
>>> Thomas,
>>>
>>> On Mon, 29 Oct 2007, Thomas Bächler wrote:
>>>> x86_64 fails to compile for me with this error:
>>>>
>>>> CC arch/x86/kernel/vsyscall_64.o
>>>> {standard input}: Assembler messages:
>>>> {standard input}:434: Error: symbol `vsysc2' is already defined
>>>> make[1]: *** [arch/x86/kernel/vsyscall_64.o] Error 1
>>>> make: *** [arch/x86/kernel] Error 2
>>>>
>>>> The .config is attached. What's wrong?
>>> Very recent gcc I guess ? Patch below should fix this.
>> Indeed very recent. The patch doesn't solve the problem though:
>> CC arch/x86/kernel/vsyscall_64.o
>> {standard input}: Assembler messages:
>> {standard input}:436: Error: symbol `vsysc2' is already defined
>> make[1]: *** [arch/x86/kernel/vsyscall_64.o] Error 1
>> make: *** [arch/x86/kernel] Error 2
>>
>> gcc (GCC) 4.2.2
>> GNU assembler (GNU Binutils) 2.18
>
> Doh, no idea right now. Ingo has a 4.2.2 toolchain handy and will
> check tomorrow.
>
> Thanks,
>
> tglx
I just remembered, a friend of mine got it to compile with the exact
same toolchain, but with a different configuration (which I don't have).
He used a snapshot tarball from yesterday though, not the git tree.
next prev parent reply other threads:[~2007-10-30 9:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-29 21:46 2.6.24-rc1-82798a1 compile failure (x86_64) Thomas Bächler
2007-10-29 22:12 ` Thomas Gleixner
[not found] ` <47266BF6.6070206@archlinux.org>
[not found] ` <alpine.LFD.0.9999.0710300033470.3186@localhost.localdomain>
2007-10-30 9:10 ` Thomas Bächler [this message]
2007-11-03 10:04 ` Thomas Bächler
2007-11-03 12:11 ` Sam Ravnborg
2007-11-04 2:02 ` Adrian Bunk
2007-11-04 10:04 ` Ingo Molnar
2007-11-04 10:19 ` Sam Ravnborg
2007-11-04 10:31 ` David Miller
2007-11-04 11:16 ` Sam Ravnborg
2007-11-04 12:27 ` Thomas Bächler
2007-11-04 15:29 ` Adrian Bunk
2007-11-04 15:55 ` Oleg Verych
2007-11-04 16:19 ` Giacomo Catenazzi
2007-11-04 16:34 ` Adrian Bunk
2007-11-04 18:33 ` Giacomo Catenazzi
2007-11-05 4:03 ` David Miller
2007-11-04 18:10 ` Sam Ravnborg
2007-11-05 4:01 ` David Miller
2007-11-06 17:32 ` Arjan van de Ven
2007-11-07 0:12 ` Adrian Bunk
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=4726F510.9060207@archlinux.org \
--to=thomas@archlinux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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