From: Hamish Moffatt <hamish@cloud.net.au>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0002164]: DirectFB Fails with --enable-static option because of incorrect ld location
Date: Sun, 17 Feb 2008 10:50:37 +1100 [thread overview]
Message-ID: <20080216235037.GB30401@cloud.net.au> (raw)
In-Reply-To: <d338add7d7956fb6821db0c1b916ccea@busybox.net>
On Fri, Feb 15, 2008 at 07:27:40PM -0800, bugs at busybox.net wrote:
> Today i was trying to make arm926ejs toolchain with buildroot 4th feb
> snapshot. I added --enable-static option in directfb.mk file. During build
> i noticed that directfb is using root ld (/usr/bin/ld) instead of
> arm-linux-ld build by buildroot toolchain. i renamed /usr/bin/ld to
> /usr/bin/ld_orig and it failed with below error.
>
> Is there any way to make directfb makefile to consider buildroot toolchain
> built ld instead of /usr/bin/ld
> Making install in fbdev
> make[3]: Entering directory
> `/home/project/original/bldrt/buildroot/build_arm/DirectFB-1.0.1/systems/fbdev'
[..]
It looks like some (re)linking is being done at install time. Modify
directfb.mk to pass the relevant compiler/linker flags during install as
well.
Where you see:
$(STAGING_DIR)/usr/lib/libdirectfb.so: $(DIRECTFB_DIR)/.compiled
$(MAKE) DESTDIR=$(STAGING_DIR)/usr -C $(DIRECTFB_DIR) install
change this to
$(MAKE) $(TARGET_CONFIGURE_OPTS) DESTDIR=$(STAGING_DIR)/usr -C $(DIRECTFB_DIR) install
Please report if this works for you so that it can be checked in.
Hamish
--
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
prev parent reply other threads:[~2008-02-16 23:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-16 3:27 [Buildroot] [buildroot 0002164]: DirectFB Fails with --enable-static option because of incorrect ld location bugs at busybox.net
2008-02-16 23:50 ` Hamish Moffatt [this message]
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=20080216235037.GB30401@cloud.net.au \
--to=hamish@cloud.net.au \
--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