From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 5624] New: When building directfb, BR2_TARGET_LDFLAGS not used by libtool
Date: Wed, 24 Oct 2012 10:40:47 +0000 (UTC) [thread overview]
Message-ID: <bug-5624-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=5624
Summary: When building directfb, BR2_TARGET_LDFLAGS not used by
libtool
Product: buildroot
Version: 2012.08
Platform: PC
OS/Version: Linux
Status: NEW
Severity: major
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: dunk_palmer at yahoo.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Created attachment 4592
--> https://bugs.busybox.net/attachment.cgi?id=4592
Snippet of build output, showing incorrect linker invocation.
I'm using the CodeSourcery mips-4.4 toolchain, and have a little endian target,
so I set BR2_TARGET_LDFLAGS="-EL" in my .config. Works fine for most things,
however directfb fails to build; at one stage, it invokes the linker, without
the -EL argument, and the link fails because the linker (which defaults to BE)
is attempting to link LE object files.
Dodgy workaround is to replace output/host/usr/bin/mips-linux-gnu-ld with a
script that contains:
#!/bin/sh
exec /opt/CodeSourcery/mips-4.4//bin/mips-linux-gnu-ld -EL $*
Relevant build output attached. The interesting parts of my .config are:
#
# Toolchain
#
# BR2_TOOLCHAIN_BUILDROOT is not set
BR2_TOOLCHAIN_EXTERNAL=y
# BR2_TOOLCHAIN_CTNG is not set
# BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_MIPS201109 is not set
# BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_MIPS201103 is not set
BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_MIPS44=y
# BR2_TOOLCHAIN_EXTERNAL_CUSTOM is not set
# BR2_TOOLCHAIN_EXTERNAL_DOWNLOAD is not set
BR2_TOOLCHAIN_EXTERNAL_PREINSTALLED=y
BR2_TOOLCHAIN_EXTERNAL_PATH="/opt/CodeSourcery/mips-4.4/"
BR2_TOOLCHAIN_EXTERNAL_PREFIX="mips-linux-gnu"
BR2_TOOLCHAIN_EXTERNAL_GLIBC=y
BR2_TARGET_OPTIMIZATION="-pipe -EL"
BR2_TARGET_LDFLAGS="-EL"
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2012-10-24 10:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 10:40 bugzilla at busybox.net [this message]
2012-10-24 12:32 ` [Buildroot] [Bug 5624] When building directfb, BR2_TARGET_LDFLAGS not used by libtool bugzilla at busybox.net
2012-10-24 21:04 ` bugzilla at busybox.net
2012-10-24 22:00 ` bugzilla at busybox.net
2012-10-25 9:09 ` bugzilla at busybox.net
2012-10-26 7:34 ` Arnout Vandecappelle
2012-10-25 9:09 ` bugzilla at busybox.net
2012-10-26 6:56 ` bugzilla at busybox.net
2014-02-12 8:52 ` bugzilla at busybox.net
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=bug-5624-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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