From: miah <jjohnson@sunrise-linux.com>
To: nfs@lists.sourceforge.net
Subject: Re: Problems building nfs-utils 0.3.3
Date: Mon, 15 Apr 2002 06:59:10 -0700 [thread overview]
Message-ID: <20020415065910.A50298@server.sunrise-linux.com> (raw)
In-Reply-To: <3CBA9AE2.9080597C@moving-picture.com>; from james-p@moving-picture.com on Mon, Apr 15, 2002 at 10:18:26AM +0100
I actually patched rpcgen to look for cpp in the proper place (/usr/bin) (I really with the glibc people would get with it..) But for some reason creating a symlink in /lib to /usr/bin/cpp fixes the build. I guess I'll have to double check my rpcgen patch to make sure its working properly.
Thanks for pointing this out, I've been looking at this problem for longer than I had hoped and missed this.
-miah
On Mon, Apr 15, 2002 at 10:18:26AM +0100, James Pearson wrote:
> Not an expert on this sort of thing, but:
>
> > Making all in export
> > rm -f mount.h mount_clnt.c mount_xdr.c
> > ../../bin/rpcgen -h -o mount.h mount.x
> > cannot find any C preprocessor (cpp)
> > ../../bin/rpcgen -l -o mount_clnt.c mount.x
> > cannot find any C preprocessor (cpp)
> > ../../bin/rpcgen -c -o mount_xdr.c mount.x
> > cannot find any C preprocessor (cpp)
>
> looks like is part of the problem ...
>
> Do you have /lib/cpp (which on my systems is a symbolic link to
> /usr/bin/cpp) ?
>
> James Pearson
>
> _______________________________________________
> NFS maillist - NFS@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2002-04-15 13:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-13 14:40 Problems building nfs-utils 0.3.3 miah
2002-04-15 9:18 ` James Pearson
2002-04-15 13:59 ` miah [this message]
2002-04-15 14:11 ` miah
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=20020415065910.A50298@server.sunrise-linux.com \
--to=jjohnson@sunrise-linux.com \
--cc=nfs@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.