From: hjl@lucon.org (H.J. Lu)
To: ian@zembu.com (Ian Lance Taylor)
Cc: fheitka@ibm.net, binutils@sourceware.cygnus.com
Subject: Re: binutils on PowerPC Linux APUS
Date: Fri, 02 Jul 1999 08:38:00 -0000 [thread overview]
Message-ID: <19990702153803.552C257B9@ocean.lucon.org> (raw)
In-Reply-To: <19990702141618.29188.qmail@daffy.airs.com>
>
> Date: Fri, 2 Jul 1999 07:20:25 -0400
> From: "F. Heitkamp" <fheitka@ibm.net>
>
> This is make check on PowerPC Linux on APUS (Amiga with PPC PowerUP
> card). I used binutils 2.9.1.0.25, egcs-1.1.2, and glibc-2.1.1 for
> the build. The kernel version is 2.2.8d. Following the 'make check'
> results are the tar-gzipped-MIME binutils log files.
>
> Here are some lines from the binutils.log file:
>
> spawn /drives/work1/src/binutils-bin/binutils/ar rc tmpdir/artest.a tmpdir/abcdefghijklmnopqrstuvwxyz1 tmpdir/abcdefghijklmnopqrstuvwxyz2
> spawn failed
>
> In fact, according to binutils.log, DejaGnu never managed to
> successfully run a program.
>
> If you can run the program /drives/work1/src/binutils-bin/binutils/ar
> by hand, then I think the problem is in DejaGnu. For some reason, it
> is failing to actually start the program.
>
> If you can not run the program by hand, then the bug is somewhere in
> the way the programs were built.
>
I have seen that one before. Make sure you have devpts in kernel.
I have
none /dev/pts devpts gid=5,mode=620 0 0
in /etc/fstab.
--
H.J. Lu (hjl@gnu.org)
next prev parent reply other threads:[~1999-07-02 8:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-02 4:20 F. Heitkamp
1999-07-02 4:33 ` Franz Sirl
1999-07-02 6:24 ` Christopher C Chimelis
1999-07-02 7:17 ` Ian Lance Taylor
1999-07-02 8:38 ` H.J. Lu [this message]
1999-07-03 4:15 ` F. Heitkamp
1999-07-03 10:13 ` H.J. Lu
1999-07-03 13:04 ` F. Heitkamp
1999-07-13 12:09 ` Testsuite/dejagnu problems continue for me, unfortunately Christopher C Chimelis
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=19990702153803.552C257B9@ocean.lucon.org \
--to=hjl@lucon.org \
--cc=binutils@sourceware.cygnus.com \
--cc=fheitka@ibm.net \
--cc=ian@zembu.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).