From: Scott Reese <sreese@indianaheart.org>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot on Ubuntu 6.10
Date: Thu, 09 Nov 2006 07:50:09 -0500 [thread overview]
Message-ID: <45532401.6020000@indianaheart.org> (raw)
In-Reply-To: <20061108075309.GA23542@codepoet.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Erik Andersen wrote:
> On Tue Nov 07, 2006 at 08:11:08PM -0500, Scott Reese wrote:
>> In any event, just changing the /bin/sh link from dash to bash fixed all
>> of my problems with no noticeable problems on the workstation. If
>> you're having problems building on a Ubuntu 6.10 system, that's a good
>> place to start.
>
> I'm running ubuntu 6.10 on my box, with /bin/sh pointing
> to dash, and thus far I've not had any serious problems.
> If you have specific failures, I'd love to know about them,
>
> -Erik
>
> --
> Erik B. Andersen http://codepoet-consulting.com/
> --This message was written using 73% post-consumer electrons--
Greetings:
I spent the entire evening trying to reproduce the problem and could
not. I was having problems in the binutils build. It was failing to
compile the documentation. I'm willing to chalk it up to some other
problem with the 6.06->6.10 upgrade. I lost the unifdef package
somewhere in the upgrade process, but removing it didn't cause the
problem to come back, so that wasn't it.
Sorry to waste everyone's time.
- -Scott
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFUyQBS7FYdPX6+iYRAjRkAKCbSYjX3Nd+/OF9IS1yAtNhkxTQBACcC1BX
aFXO97NYL49YGXfqT68GpV4=
=hz03
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2006-11-09 12:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-08 1:11 [Buildroot] Buildroot on Ubuntu 6.10 Scott Reese
2006-11-08 2:46 ` Ashwin Bihari
2006-11-08 7:53 ` Erik Andersen
2006-11-08 8:42 ` Benjamin Delagoutte
2006-11-09 12:50 ` Scott Reese [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=45532401.6020000@indianaheart.org \
--to=sreese@indianaheart.org \
--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