From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
linux-kernel@vger.kernel.org, sam@ravnborg.org
Subject: Re: 2.6.26-rc1 on x86: ld: warning: dot moved backwards before `.text'
Date: Sat, 10 May 2008 22:23:55 +0200 [thread overview]
Message-ID: <200805102223.56494.rjw@sisk.pl> (raw)
In-Reply-To: <18470.787.498329.144701@harpo.it.uu.se>
On Saturday, 10 of May 2008, Mikael Pettersson wrote:
> Building kernel 2.6.26-rc1 on FC6/i386 causes:
>
> ld -m elf_i386 -T arch/x86/kernel/acpi/realmode/wakeup.lds arch/x86/kernel/acpi/realmode/wakeup.o arch/x86/kernel/acpi/realmode/wakemain.o arch/x86/kernel/acpi/realmode/video-mode.o arch/x86/kernel/acpi/realmode/copy.o arch/x86/kernel/acpi/realmode/video-vga.o arch/x86/kernel/acpi/realmode/video-vesa.o arch/x86/kernel/acpi/realmode/video-bios.o -o arch/x86/kernel/acpi/realmode/wakeup.elf
> ld: warning: dot moved backwards before `.text'
> ld: warning: dot moved backwards before `.text'
> ld: warning: dot moved backwards before `.text'
>
> This is with gcc-4.2.3 and binutils-2.17.50.0.6-5.fc6 20061020.
>
> The resulting kernel hasn't broken on me yet, however.
It shouldn't. Have you tried to suspend to RAM?
> A search through the LKML archives showed that this was reported
> for 2.6.25-rc3-mm1, but I couldn't find any discussion about it
> after that:
>
> <http://marc.info/?l=linux-kernel&m=120470303728010&w=2>
>
> The .config causing this warning is available in
> <http://user.it.uu.se/~mikpe/linux/ale/config-2.6.26-rc1>
Well, we don't really know why this happens. It surely doesn't happen with
newer toolchains (as of OpenSUSE 10.3 for example).
Thanks,
Rafael
next prev parent reply other threads:[~2008-05-10 20:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-10 20:18 2.6.26-rc1 on x86: ld: warning: dot moved backwards before `.text' Mikael Pettersson
2008-05-10 20:23 ` Rafael J. Wysocki [this message]
2008-05-10 20:25 ` H. Peter Anvin
2008-05-10 20:56 ` Rafael J. Wysocki
2008-05-11 18:52 ` Pavel Machek
2008-05-10 21:16 ` Sam Ravnborg
2008-05-11 15:44 ` Cyrill Gorcunov
2008-05-11 18:15 ` H. Peter Anvin
2008-05-11 18:24 ` Cyrill Gorcunov
2008-05-11 18:25 ` H. Peter Anvin
2008-05-11 18:29 ` Cyrill Gorcunov
2008-05-11 21:22 ` Rafael J. Wysocki
2008-05-12 4:15 ` Cyrill Gorcunov
2008-05-12 6:16 ` Cyrill Gorcunov
2008-05-12 6:52 ` Pavel Machek
2008-05-11 18:54 ` Pavel Machek
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=200805102223.56494.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@it.uu.se \
--cc=mingo@redhat.com \
--cc=sam@ravnborg.org \
--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