From: rdkehn at yahoo.com <rdkehn@yahoo.com>
To: buildroot@busybox.net
Subject: [Buildroot] ldconfig - unknown machine 40
Date: Tue, 10 Mar 2015 18:49:50 -0500 [thread overview]
Message-ID: <20150310234950.GA20190@dkarchlinux64.currentcomm.com> (raw)
Thomas,
Thomas Petazzoni <thomas.petazzoni@...> writes:
>
> Dear Matthias 'muh' Pauligk,
>
> On Thu, 15 Jan 2015 06:23:54 -0800 (PST), Matthias 'muh' Pauligk wrote:
>
> > 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:
>
> The problem is unfortunately not that simple: yes you have a ldconfig
> for glibc toolchains. But not for uClibc based toolchains.
>
> Best regards,
>
> Thomas
>
... sorry for dredging up an old thread; however, I was wondering if
you would mind commenting more on ldconfig for glibc toolchains.
Should a host ldconfig be build for Buildroot built glibc
toolchains?
I built a glibc 2.20 arm-buildroot-linux-gnueabihf toolchain from
Buildroot 2015.05-git-00331-gcef6a78 and I don't have an
arm-buildroot-linux-gnueabihf-ldconfig. Thus, when the build gets
to the finalizing target directory stage, I observe the 'ldconfig -
unknown machine 40' message.
:
:
# Mandatory configuration file and auxilliary cache directory
# for recent versions of ldconfig
touch /home/dkehn/devel/buildroot/output/target/etc/ld.so.conf
mkdir -p
/home/dkehn/devel/buildroot/output/target/var/cache/ldconfig
if [ -x
"/home/dkehn/devel/buildroot/output/host/usr/bin/arm-buildroot-linux-gnueabihf-ldconfig"
]; \
then \
/home/dkehn/devel/buildroot/output/host/usr/bin/arm-buildroot-linux-gnueabihf-ldconfig
-r /home/dkehn/devel/buildroot/output/target; \
else \
/sbin/ldconfig -r /home/dkehn/devel/buildroot/output/target;
\
fi
/sbin/ldconfig:
/usr/lib/libglibmm_generate_extra_defs-2.4.so.1 is for
unknown machine 40.
/sbin/ldconfig: /usr/lib/libxslt.so.1.1.28 is for unknown
machine 40.
:
:
I thought arm-buildroot-linux-gnueabihf-ldconfig would be present.
Thanks and Regards,
..doug
next reply other threads:[~2015-03-10 23:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 23:49 rdkehn at yahoo.com [this message]
-- strict thread matches above, loose matches on Subject: below --
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
2015-01-16 8:37 ` Thomas Petazzoni
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=20150310234950.GA20190@dkarchlinux64.currentcomm.com \
--to=rdkehn@yahoo.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.