Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] ldconfig errors
Date: Tue, 17 Aug 2010 14:10:45 +0300	[thread overview]
Message-ID: <20100817111045.GC9631@jasper.tkos.co.il> (raw)
In-Reply-To: <000501cb3def$b74a9eb0$25dfdc10$@pauljones.id.au>

Hi Paul,

On Tue, Aug 17, 2010 at 07:36:47PM +1000, Paul Jones wrote:
> I seem to have run into the ldconfig error while using a crosstool-ng
> external toolchain (uclibc based). I remember this being discussed a while
> back but can't seem to find a solution, short of using an internal
> toolchain.
> 
> This is the error:
> 
> if [ -x
> "/media/dev/arm-unknown-linux-uclibcgnueabi/bin/arm-unknown-linux-uclibcgnue
> abi-ldconfig" ]; \
> 
>         then \
> 
>  
> /media/dev/arm-unknown-linux-uclibcgnueabi/bin/arm-unknown-linux-uclibcgnuea
> bi-ldconfig -r /media/dev/buildroot-arm/output/target 2>/dev/null; \
> 
>         else \
> 
>                 /sbin/ldconfig -r /media/dev/buildroot-arm/output/target
> 2>/dev/null; \
> 
>         fi
> 
> make: *** [target-finalize] Error 1
> 
> I can't use the host version unless I run as root. This is on a Gentoo
> x86_64 host with ARM target.
> 
> Any suggestions?

See http://lists.busybox.net/pipermail/buildroot/2010-June/035443.html and 
http://lists.busybox.net/pipermail/buildroot/2010-August/036726.html.

I hope this helps.

baruch

-- 
                                                     ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

      reply	other threads:[~2010-08-17 11:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-17  9:36 [Buildroot] ldconfig errors Paul Jones
2010-08-17 11:10 ` Baruch Siach [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=20100817111045.GC9631@jasper.tkos.co.il \
    --to=baruch@tkos.co.il \
    --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