From: Jurij Smakov <jurij@lokmail.net>
To: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Glibc 2.2.4-2 Woes...
Date: Mon, 08 Oct 2001 04:26:07 -0400 [thread overview]
Message-ID: <200110080826.EAA26514@mail.lokmail.net> (raw)
>
> M,
>
> I see what you mean now.
> I have glibc 2.2.4-2 compiling all the way to the point where it
> starts churning thorugh:
>
> make -C sunrpc others
Hi!
Stuff fails in sunrpc, because it tries to do something like
rpcgen -Y `gcc -print-file-name=cpp | sed 's|/cpp$||'`
Argument to -Y option should be the dir, where cpp is located, so the
build expects, that `gcc -print-file-name=cpp` will return a full
path to cpp. Well, it does not. It spits out "cpp" and then sed
replacement fails, so the actual command being run is
rpcgen -Y cpp/cpp
It is probably easily fixable, but there is also a simple workaround:
cd .../glibc/sunrpc (NOT glibc-build)
mkdir cpp
cd cpp
ln -s /path_to_real_cpp/cpp cpp
After that I was able to finish the build.
Best regards,
Jurij.
next reply other threads:[~2001-10-08 8:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-08 8:26 Jurij Smakov [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-06 17:55 [parisc-linux] Glibc 2.2.4-2 Woes Carlos O'Donell Jr.
2001-10-07 4:47 ` Randolph Chung
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=200110080826.EAA26514@mail.lokmail.net \
--to=jurij@lokmail.net \
--cc=parisc-linux@lists.parisc-linux.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