From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Alex Thiel <stderr@web.de>
Cc: nfs@lists.sourceforge.net
Subject: Re: nfs-utils 1.0.3 compile error w/gcc-3.2.2
Date: Fri, 28 Mar 2003 10:13:26 -0500 [thread overview]
Message-ID: <3E846696.6010900@lucidpixels.com> (raw)
In-Reply-To: 200303281557.29049.stderr@web.de
CPP is in my path, is it hardcoded or something?
war@war:~$ which cpp
/vapp/bin/cpp
war@war:~$ cpp --version
cpp (GCC) 3.2.2
Copyright (C) 2002 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
war@war:~$ echo $PATH
/vapp/bin:/vapp/sbin:/appc/netscape-4.8:/appc/realplayer-8.0:/appc/j2re-1.4.1/bin:/appc/jdk-1.4.1/bin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin:/usr/local/bin:/usr/local/sbin
war@war:~$
Alex Thiel wrote:
>On Friday 28 March 2003 14:29, Justin Piszcz wrote:
>
>
>>-rw-r--r-- 1 war wheel 2.7k Mar 28 08:24 log.bz2
>>
>>The error is contained in the attachment.
>>
>>
>
>Did you notice this in your log:
>
>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)
>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
>Make sure cpp is in your search path.
>
> Alex
>
>
>
>
>
-------------------------------------------------------
This SF.net email is sponsored by:
The Definitive IT and Networking Event. Be There!
NetWorld+Interop Las Vegas 2003 -- Register today!
http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-03-28 15:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-28 13:29 nfs-utils 1.0.3 compile error w/gcc-3.2.2 Justin Piszcz
2003-03-28 14:57 ` Alex Thiel
2003-03-28 15:13 ` Justin Piszcz [this message]
2003-03-28 19:58 ` Alex Thiel
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=3E846696.6010900@lucidpixels.com \
--to=jpiszcz@lucidpixels.com \
--cc=nfs@lists.sourceforge.net \
--cc=stderr@web.de \
/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