From: Alexander Holler <holler@ahsoftware.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V3 1/3] arm926ejs: fix linker file for newer ld support
Date: Thu, 04 Nov 2010 19:42:48 +0100 [thread overview]
Message-ID: <4CD2FEA8.8050106@ahsoftware.de> (raw)
In-Reply-To: <4CD2FD7E.5080309@ahsoftware.de>
Am 04.11.2010 19:37, schrieb Alexander Holler:
>> You're still using a locally-built toolchain different from CS and ELDK
>> toolhcains that were tested so far, right? There is a warning at the
>
> Yes, I'm still using Gentoo to compile u-boot native on that board.
>
>> linker stage in the build log you sent me:
>>
>> ld: warning: creating a DT_TEXTREL in object.
>>
>> which I don't have using the CS 2010q1 toolchain.
>
> This warning comes through one of the patches Gentoo applies to
> binutils. That patch can be found inside the archive here:
>
> ftp://de-mirror.org/distro/gentoo/distfiles/binutils-2.20.1-patches-1.1.tar.bz2
If I read that patch (66_*) correctly, it's the same as when using
--warn-shared-textrel in LDFLAGS.
Regards,
Alexander
next prev parent reply other threads:[~2010-11-04 18:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-03 18:24 [U-Boot] [PATCH V3 1/3] arm926ejs: fix linker file for newer ld support Albert Aribaud
2010-11-03 18:24 ` [U-Boot] [PATCH V3 2/3] tx25: " Albert Aribaud
2010-11-03 18:24 ` [U-Boot] [PATCH V3 3/3] tx25: increase u-boot NAND size to match current build sizes Albert Aribaud
2010-11-03 18:27 ` [U-Boot] [PATCH V3 1/3] arm926ejs: fix linker file for newer ld support Albert ARIBAUD
2010-11-04 10:26 ` Alexander Holler
2010-11-04 10:46 ` Alexander Holler
2010-11-04 12:40 ` Albert ARIBAUD
2010-11-04 12:47 ` Alexander Holler
2010-11-04 12:55 ` Albert ARIBAUD
2010-11-04 13:18 ` Alexander Holler
2010-11-04 16:56 ` Albert ARIBAUD
2010-11-04 18:37 ` Alexander Holler
2010-11-04 18:42 ` Alexander Holler [this message]
2010-11-04 19:20 ` Albert ARIBAUD
2010-11-04 19:39 ` Alexander Holler
2010-11-04 22:06 ` Albert ARIBAUD
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=4CD2FEA8.8050106@ahsoftware.de \
--to=holler@ahsoftware.de \
--cc=u-boot@lists.denx.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