All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Broken symbolic links in generated toolchain
Date: Fri, 30 Jan 2009 12:24:15 +0100	[thread overview]
Message-ID: <20090130122415.2c585016@surf> (raw)

Hi,

I just grabbed -rc2 and simply generated a MIPS toolchain (no
packages).

After generation, the STAGING_DIR has two broken symbolic links:

 mips-linux -> mips-linux-uclibc
 usr/bin/cc -> usr/bin/gcc

While not preventing the toolchain from working, it always seems
strange to have broken symlinks.

.config file attached.

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: .config
Type: application/octet-stream
Size: 19050 bytes
Desc: not available
Url : http://lists.busybox.net/pipermail/buildroot/attachments/20090130/28750706/attachment-0001.obj 

             reply	other threads:[~2009-01-30 11:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-30 11:24 Thomas Petazzoni [this message]
2009-01-30 13:41 ` [Buildroot] Broken symbolic links in generated toolchain Peter Korsgaard
2009-01-30 14:34   ` 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=20090130122415.2c585016@surf \
    --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.