All of lore.kernel.org
 help / color / mirror / Atom feed
From: cir.vfi at gmail.com <cir.vfi@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] ldconfig - unknown machine 40
Date: Wed, 3 Jul 2013 14:49:26 -0700 (PDT)	[thread overview]
Message-ID: <1372888166340-47834.post@n4.nabble.com> (raw)
In-Reply-To: <CAPNngROZPybYo4pkY3GXFgH8yONY9bXwMU7o23hmQ39J=0BN=Q@mail.gmail.com>

Milton Soares Filho wrote
> On 2 July 2013 08:49, Ciar?n Rehill &lt;

> cir.vfi@

> &gt; wrote:
>> Is it normal not to supply a cross-ldconfig with a toolchain release or
>> is there a standard policy on this?
> 
> I haven't found a cross-ldconfig within both sh4 and broadcom
> toolchains which I have available.

Same story with the cross compiler in the yum repos for Fedora
(gcc-arm-linux-gnu): no ldconfig.

Anyway, what seems to be a (dirty) workaround is to take the
"/sbin/ldconfig.real" from a Ubuntu 12.04 system and place it into the
cross-compiler bin/ directory, renaming with the toolchain tuple,
"~/CodeSourcery/Sourcery_G++/bin/arm-none-linux-gnueabi-ldconfig" in this
case.  The file can be extracted from a .rpm or .deb for the appropriate
version.
I know it's wrong, but it gets over this bump in the absence of a better
solution.  Hopefully one of the elders of the list will suggest something
more appropriate.



--
View this message in context: http://buildroot-busybox.2317881.n4.nabble.com/ldconfig-unknown-machine-40-tp47588p47834.html
Sent from the Buildroot (busybox) mailing list archive at Nabble.com.

  reply	other threads:[~2013-07-03 21:49 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 [this message]
2015-01-15 14:23 ` Matthias 'muh' Pauligk
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=1372888166340-47834.post@n4.nabble.com \
    --to=cir.vfi@gmail.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.