Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Missing x86_64-linux-uclibc-gcc and uClibc-locale-20081111-64-el.tgz
Date: Sun, 18 Oct 2009 11:20:46 +0200	[thread overview]
Message-ID: <20091018092046.GG3498@mx.loc> (raw)
In-Reply-To: <4ADAC70C.1060601@renta.net>

On Sun, Oct 18, 2009 at 05:43:08PM +1000, Mark Constable wrote:
>Any hints how to work around this?

http://lists.uclibc.org/pipermail/uclibc/2008-December/041624.html
>
>make[1]: Leaving directory `/home/sources/srcpkgs/eth-os/cli/src/buildroot-2009.08/toolchain_build_x86_64/uClibc-0.9.30.1'
>touch /home/sources/srcpkgs/eth-os/cli/src/buildroot-2009.08/toolchain_build_x86_64/uClibc-0.9.30.1/.config
>set -x && /usr/bin/make -j1 -C /home/sources/srcpkgs/eth-os/cli/src/buildroot-2009.08/toolchain_build_x86_64/uClibc-0.9.30.1 \
>               PREFIX=/home/sources/srcpkgs/eth-os/cli/src/buildroot-2009.08/toolchain_build_x86_64/uClibc_dev/ \
>               DEVEL_PREFIX=/usr/ \
>               RUNTIME_PREFIX=/home/sources/srcpkgs/eth-os/cli/src/buildroot-2009.08/toolchain_build_x86_64/uClibc_dev/ \
>               HOSTCC="/usr/bin/gcc" headers \
>               install_headers
>+ /usr/bin/make -j1 -C /home/sources/srcpkgs/eth-os/cli/src/buildroot-2009.08/toolchain_build_x86_64/uClibc-0.9.30.1 PREFIX=/home/sources/srcpkgs/eth-os/cli/src/buildroot-2009.08/toolchain_build_x86_64/uClibc_dev/ DEVEL_PREFIX=/usr/ RUNTIME_PREFIX=/home/sources/srcpkgs/eth-os/cli/src/buildroot-2009.08/toolchain_build_x86_64/uClibc_dev/ HOSTCC=/usr/bin/gcc headers install_headers
>/bin/sh: /home/sources/srcpkgs/eth-os/cli/src/buildroot-2009.08/build_x86_64/staging_dir/usr/bin/x86_64-linux-uclibc-gcc: No such file or directory
>make[1]: /home/sources/srcpkgs/eth-os/cli/src/buildroot-2009.08/build_x86_64/staging_dir/usr/bin/x86_64-linux-uclibc-gcc: Command not found
>make[1]: Entering directory `/home/sources/srcpkgs/eth-os/cli/src/buildroot-2009.08/toolchain_build_x86_64/uClibc-0.9.30.1'
>make[1]: /home/sources/srcpkgs/eth-os/cli/src/buildroot-2009.08/build_x86_64/staging_dir/usr/bin/x86_64-linux-uclibc-gcc: Command not found
>( cd extra/locale/; wget --passive-ftp http://www.uclibc.org/downloads/uClibc-locale-20081111-64-el.tgz )
>--2009-10-18 17:37:31--  http://www.uclibc.org/downloads/uClibc-locale-20081111-64-el.tgz
>Resolving www.uclibc.org... 140.211.167.224
>Connecting to www.uclibc.org|140.211.167.224|:80... connected.
>HTTP request sent, awaiting response... 404 Not Found
>2009-10-18 17:37:32 ERROR 404: Not Found.
>
>
>--markc
>_______________________________________________
>buildroot mailing list
>buildroot at busybox.net
>http://lists.busybox.net/mailman/listinfo/buildroot

  reply	other threads:[~2009-10-18  9:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-18  7:43 [Buildroot] Missing x86_64-linux-uclibc-gcc and uClibc-locale-20081111-64-el.tgz Mark Constable
2009-10-18  9:20 ` Bernhard Reutner-Fischer [this message]
2009-10-18  9:50   ` Mark Constable
  -- strict thread matches above, loose matches on Subject: below --
2009-10-17 16:54 Mark Constable

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=20091018092046.GG3498@mx.loc \
    --to=rep.dot.nop@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox