All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Dangling symbolic links in the generated toolchain
Date: Thu, 13 Mar 2008 14:52:59 +0100	[thread overview]
Message-ID: <20080313145259.0af99b35@crazy> (raw)

Hi,

When creating a toolchain with the attached config file, there are some
dangling symlinks in build_arm/staging_dir/ :

$ symlinks -r build_arm/staging_dir/ | grep ^dangling
dangling: build_arm/staging_dir/arm-linux -> arm-linux-uclibcgnueabi
dangling: build_arm/staging_dir/usr/bin/cc -> gcc

The former should probably point to usr/arm-linux-uclibcgnueabi
instead. No idea for the latter, though.

Sincerly,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Free Embedded Linux Training Materials
on http://free-electrons.com/training
(More than 1500 pages!)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://busybox.net/lists/buildroot/attachments/20080313/dbce62a6/attachment.pgp 

                 reply	other threads:[~2008-03-13 13:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20080313145259.0af99b35@crazy \
    --to=thomas.petazzoni@free-electrons.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.