From: Martin Costabel <costabel@wanadoo.fr>
To: linuxppc-dev@lists.linuxppc.org
Subject: Scilab compiling problem
Date: Thu, 13 May 1999 02:13:31 +0200 [thread overview]
Message-ID: <373A192B.F6940925@wanadoo.fr> (raw)
Since I had scilab running on linuxppc-R5 a long time ago, I wanted to
give the src.rpm from the redhat powertools directory a try. After a
little tweaking, it compiles OK and goes almost all the way through the
process of building the binary rpm.
Right at the end, it stops after the following lines
+ cd /var/tmp/scilab-root/usr/bin
+ ln -s ../lib/scilab-2.4.1/bin/scilab scilab
+ exit 0
Processing files: scilab
Finding provides...
Finding requires...
BFD: /var/tmp/scilab-root/usr/lib/scilab-2.4.1/bin/SEpsf: invalid string
offset 2147554304 >= 256 for section `'
BFD: /var/tmp/scilab-root/usr/lib/scilab-2.4.1/bin/SEpsf: invalid string
offset 2147561472 >= 256 for section `'
BFD: /var/tmp/scilab-root/usr/lib/scilab-2.4.1/bin/SEpsf: invalid string
offset 2147569664 >= 256 for section `'
BFD: /var/tmp/scilab-root/usr/lib/scilab-2.4.1/bin/SEpsf: invalid string
offset 2147612672 >= 256 for section `'
BFD: /var/tmp/scilab-root/usr/lib/scilab-2.4.1/bin/SEpsf: invalid string
offset 2147706880 >= 256 for section `'
After this it sits there and does nothing until killed by ctrl-C.
Does anyone know what this means? What is BFD?
Is this a bug in a) rpm b) binutils c) egcs d) somewhere else?
The file .../SEpsf is a binary which seems to run OK.
--
Martin
--
Martin
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
next reply other threads:[~1999-05-13 0:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-05-13 0:13 Martin Costabel [this message]
1999-05-13 13:54 ` Scilab compiling problem Martin Costabel
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=373A192B.F6940925@wanadoo.fr \
--to=costabel@wanadoo.fr \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).