From: Bambero <bambero@tlen.pl>
To: binutils@sourceware.org
Subject: problem with ar
Date: Wed, 27 Apr 2005 21:37:00 -0000 [thread overview]
Message-ID: <426FFBE1.9010608@tlen.pl> (raw)
Hi
I just compiled some packages for my embeded system using
gentoo-uclibc-stage3.
Everything i fine but when I chroot to my new system and try to compile
ex. sed
"ar" returns me an error:
rm -f libsed.a
ar cru libsed.a getopt1.o getopt.o utils.o strverscmp.o regex.o
ar: libsed.a: No such file or directory
make[2]: *** [libsed.a] Error 1
make[2]: Leaving directory `/usr/local/src/sed/sed-4.1.4/lib'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/local/src/sed/sed-4.1.4'
make: *** [all] Error 2
when I try to do that by hand the error is the same:
[root@pr:/usr/local/src/sed/sed-4.1.4/lib#] ar cru libsed.a getopt1.o
getopt.o utils.o strverscmp.o regex.o
ar: libsed.a: No such file or directory
[root@pr:/usr/local/src/sed/sed-4.1.4/lib#]
but when i try:
[root@pr:/usr/local/src/sed/sed-4.1.4/lib#] ar cru libsed.a
[root@pr:/usr/local/src/sed/sed-4.1.4/lib#]
everything is fine.
Anyone knows where is the problem ?
Bambero
next reply other threads:[~2005-04-27 20:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-27 21:37 Bambero [this message]
2005-04-27 23:43 ` Problem with 2.16 MIPS as (MIPS TLS support) Khem Raj
2005-04-28 1:08 ` Daniel Jacobowitz
2005-05-05 10:12 ` problem with ar Nick Clifton
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=426FFBE1.9010608@tlen.pl \
--to=bambero@tlen.pl \
--cc=binutils@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).