From: Matthias 'muh' Pauligk <paulms@idmt.fraunhofer.de>
To: buildroot@busybox.net
Subject: [Buildroot] ldconfig - unknown machine 40
Date: Thu, 15 Jan 2015 06:23:54 -0800 (PST) [thread overview]
Message-ID: <1421331834928-90477.post@n4.nabble.com> (raw)
In-Reply-To: <loom.20130628T172450-675@post.gmane.org>
Hi,
I faced the same problem using buildroot's toolchain.
The ld-config is present in the host directory, but the Makefile is looking
at the wrong path.
So I made a small patch to fix this issue, which is working fine for me:
--- a/Makefile
+++ b/Makefile
@@ -161,6 +161,7 @@
# initial definition so that 'make clean' works for most users, even
without
# .config. HOST_DIR will be overwritten later when .config is included.
HOST_DIR := $(BASE_DIR)/host
+LDCONF_DIR := $(HOST_DIR)/usr/arm-buildroot-linux-gnueabi/sysroot/sbin
LEGAL_INFO_DIR = $(BASE_DIR)/legal-info
REDIST_SOURCES_DIR_TARGET = $(LEGAL_INFO_DIR)/sources
@@ -597,9 +598,9 @@
# for recent versions of ldconfig
touch $(TARGET_DIR)/etc/ld.so.conf
mkdir -p $(TARGET_DIR)/var/cache/ldconfig
- if [ -x "$(TARGET_CROSS)ldconfig" ]; \
+ if [ -x "$(LDCONF_DIR)/ldconfig" ]; \
then \
- $(TARGET_CROSS)ldconfig -r $(TARGET_DIR); \
+ $(LDCONF_DIR)/ldconfig -r $(TARGET_DIR); \
else \
/sbin/ldconfig -r $(TARGET_DIR); \
fi
Just apply it in buildroot's root directory.
Maybe this is also working for external toolchains, depending on where
ld-config is located there.
Best regards.
--
View this message in context: http://buildroot-busybox.2317881.n4.nabble.com/ldconfig-unknown-machine-40-tp47588p90477.html
Sent from the Buildroot (busybox) mailing list archive at Nabble.com.
next prev parent reply other threads:[~2015-01-15 14:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-28 16:55 [Buildroot] ldconfig - unknown machine 40 Ciarán Rehill
2013-07-01 22:25 ` Milton Soares Filho
2013-07-02 11:49 ` Ciarán Rehill
2013-07-02 16:31 ` Milton Soares Filho
2013-07-03 21:49 ` cir.vfi at gmail.com
2015-01-15 14:23 ` Matthias 'muh' Pauligk [this message]
2015-01-16 8:37 ` Thomas Petazzoni
-- strict thread matches above, loose matches on Subject: below --
2015-03-10 23:49 rdkehn at yahoo.com
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=1421331834928-90477.post@n4.nabble.com \
--to=paulms@idmt.fraunhofer.de \
--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