From: Jason Pepas <cell@ices.utexas.edu>
To: gentoo-mips@lists.gentoo.org
Subject: [gentoo-mips] bootstrap.sh on asus wl500g
Date: Fri, 16 Sep 2005 08:34:43 -0500 [thread overview]
Message-ID: <20050916133443.GA1024@ices.utexas.edu> (raw)
Hi,
I have an asus wl500g (same chip as the linksys wrt54g). I put openwrt
on it and chrooted into a
experimental/mips/embedded/stages/stage1-mipsel-uclibc-2005.0.tar.bz2
tarball, with the idea of changing the profile and rebuiling.
I set up make.conf like so:
CFLAGS="-Os -pipe -march=mips1"
CHOST="mipsel-unknown-linux-gnu"
and the profile like so:
make.profile -> /usr/portage/profiles/default-linux/mips/2005.0
then ran scripts/bootstrap.sh
gnuconfig had some bus errors, but didn't stop the script:
>>> Install gnuconfig-20050602 into
>>> /var/tmp/portage/gnuconfig-20050602/image/ category sys-devel
man:
prepallstrip:
strip: strip --strip-unneeded
strip: strip --strip-unneeded
usr/share/gnuconfig/config.sub
/usr/lib/portage/bin/prepstrip: line 19: 12405 Bus error
${STRIP} -g "${x}"
usr/share/gnuconfig/config.sub
/usr/lib/portage/bin/prepstrip: line 19: 12406 Bus error
${STRIP} "${x}"
usr/share/gnuconfig/config.sub
/usr/lib/portage/bin/prepstrip: line 19: 12407 Bus error
${STRIP} ${PORTAGE_STRIP_FLAGS} "${x}"
readelf: Error: Unable to read in 0x656e bytes of section headers
readelf: Error: Not an ELF file - it has the wrong magic bytes at the
start
usr/share/gnuconfig/config.guess
/usr/lib/portage/bin/prepstrip: line 19: 12411 Bus error
${STRIP} -g "${x}"
usr/share/gnuconfig/config.guess
/usr/lib/portage/bin/prepstrip: line 19: 12412 Bus error
${STRIP} "${x}"
usr/share/gnuconfig/config.guess
/usr/lib/portage/bin/prepstrip: line 19: 12413 Bus error
${STRIP} ${PORTAGE_STRIP_FLAGS} "${x}"
readelf: Error: Unable to read in 0x6d65 bytes of section headers
readelf: Error: Not an ELF file - it has the wrong magic bytes at the
start
>>> Completed installing gnuconfig-20050602 into
>>> /var/tmp/portage/gnuconfig-20050602/image/
and glibc failed during configure:
checking for suffix of object files... configure: error: cannot compute
suffix of object files: cannot compile
See `config.log' for more details.
!!! ERROR: sys-libs/glibc-2.3.5 failed.
!!! Function glibc_do_configure, Line 938, Exitcode 1
!!! failed to configure glibc
any ideas? I see the mips project website was just updated today, and I
just realized last night that the cobalt images are little endian (the
asus wl500g is little endian), so I'll try chrooting into one of those
images next.
Thanks,
Jason Pepas
--
gentoo-mips@gentoo.org mailing list
next reply other threads:[~2005-09-16 13:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-16 13:34 Jason Pepas [this message]
2005-09-16 13:42 ` [gentoo-mips] bootstrap.sh on asus wl500g Jason Pepas
2005-09-16 13:48 ` Jason Pepas
2005-09-16 13:48 ` Stephen P. Becker
2005-09-16 13:52 ` Stephen P. Becker
2005-09-16 14:01 ` Jason Pepas
2005-09-16 14:28 ` Stephen P. Becker
2005-09-16 14:44 ` Jason Pepas
2005-09-16 15:44 ` Hardave Riar
2005-09-16 16:28 ` Jason Pepas
2005-09-16 19:00 ` Stephen P. Becker
2005-09-16 13:52 ` Hardave Riar
2005-09-16 14:02 ` Stuart Longland
2005-09-16 14:07 ` Jason Pepas
2005-09-16 14:25 ` Stephen P. Becker
2005-09-16 14:39 ` Jason Pepas
2005-09-16 15:37 ` Hardave Riar
2005-09-16 15:53 ` Jason Pepas
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=20050916133443.GA1024@ices.utexas.edu \
--to=cell@ices.utexas.edu \
--cc=gentoo-mips@lists.gentoo.org \
/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