All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Pull request: u-boot-net
Date: Tue, 5 Jan 2016 08:18:21 -0500	[thread overview]
Message-ID: <20160105131821.GH4093@bill-the-cat> (raw)
In-Reply-To: <CAEUhbmXgyEY82DEy3ijFjkM_Mwq2cOcpviEWWSGRLp6vd2C6aQ@mail.gmail.com>

On Tue, Jan 05, 2016 at 12:08:24PM +0800, Bin Meng wrote:
> Hi Tom,
> 
> On Mon, Jan 4, 2016 at 10:24 PM, Tom Rini <trini@konsulko.com> wrote:
> > On Mon, Jan 04, 2016 at 04:31:05PM +0800, Bin Meng wrote:
> > [snip]
> >> $ ./install.sh -d /share/toolchain/eldk-5.6 -s toolchain -r - -a i686
> >> powerpc-4xx
> >> *** Installing ./targets/powerpc-4xx/eldk-eglibc-i686-powerpc-toolchain-5.6.sh
> >>     into /share/toolchain/eldk-5.6/powerpc-4xx
> >> tar: ./sysroots: Cannot mkdir: Read-only file system
> > [snip]
> >> Lots of 'Cannot mkdir: No such file or directory' message are shown on
> >> the console. I am pretty sure I have RW rights on the
> >> /share/toolchain/eldk-5.6 directory. Anything I am missing here?
> >
> > Well, please confirm that you can write to /sysroots/ :)  IIRC the
> > installer doesn't invoke sudo by itself, btw..
> 
> The install.sh prompts ./sysroots/, not /sysroots/. ./sysroots/ should
> point to the installation root where I definitely have the write
> permission.
> 
> Today I switched to another machine with a Ubuntu 12.04, and with the
> same iso and command I installed ELDK successfully without any error
> message like "Cannot mkdir: Read-only file system". But when I used
> the ELDK toolchain to build U-Boot iocon, I got:
> 
> /buildarea1/bmeng/eldk-5.6/powerpc-4xx/sysroots/i686-eldk-linux/usr/bin/powerpc-linux/powerpc-linux-ld.bfd
>   -m32 -melf32ppclinux -g -Ttext 0x40000 -o
> examples/standalone/hello_world -e hello_world
> examples/standalone/hello_world.o examples/standalone/libstubs.o -L .
> -lgcc
> /buildarea1/bmeng/eldk-5.6/powerpc-4xx/sysroots/i686-eldk-linux/usr/bin/powerpc-linux/powerpc-linux-ld.bfd:
> cannot find -lgcc
> make[2]: *** [examples/standalone/hello_world] Error 1
> make[1]: *** [examples/standalone] Error 2
> make: *** [examples] Error 2
> 
> It did not help whether I just source
> "environment-setup-ppc440e-linux" in the ELDK installation tree, or
> just simply "export CROSS_COMPILE=path/to/ELDK/toolchain" before
> building U-Boot.

I've never had a problem installing and using
eldk-eglibc-i686-powerpc-toolchain-5.6.sh (or 5.5 and so on).

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20160105/4584f746/attachment.sig>

  reply	other threads:[~2016-01-05 13:18 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-22 17:58 [U-Boot] Pull request: u-boot-net Joe Hershberger
2015-12-24  3:47 ` Tom Rini
2015-12-29  3:02   ` Joe Hershberger
2015-12-29 14:09     ` Tom Rini
2016-01-02 17:09 ` Tom Rini
2016-01-04  2:35   ` Bin Meng
2016-01-04  3:46     ` Tom Rini
2016-01-04  3:56       ` Bin Meng
2016-01-04  8:31         ` Bin Meng
2016-01-04 14:24           ` Tom Rini
2016-01-05  4:08             ` Bin Meng
2016-01-05 13:18               ` Tom Rini [this message]
2016-01-04 11:46         ` Dirk Eibach
2016-01-04 13:48           ` Bin Meng
2016-01-04 14:22             ` Tom Rini
2016-01-05  4:18               ` Bin Meng
2016-01-05 13:18                 ` Tom Rini
2016-01-07  2:49                   ` Bin Meng
2016-01-07 16:29                     ` Tom Rini
2016-01-13 20:58                       ` Joe Hershberger
2016-01-13 23:01                         ` Tom Rini
2016-01-13 23:10                         ` Tom Rini
2016-01-14 13:20                         ` Tom Rini
2016-01-04 14:32         ` Tom Rini
  -- strict thread matches above, loose matches on Subject: below --
2012-04-04 16:06 Joe Hershberger
2012-04-09 15:16 ` Wolfgang Denk

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=20160105131821.GH4093@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /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.