strange compile error with pppd

strange compile error with pppd

Post by Ian Mortime » Tue, 25 Jan 2000 04:00:00

Hi all,

I've been trying to get pppd 2.3.9 to compile but I'm getting a strange
compiler error:

cd chat; make  all
make[1]: Entering directory `/home/ian/ppp-2.3.9/chat'
cc -c -O2 -g -pipe -DTERMIOS                    
-DSIGTYPE=void                  -UNO_SLEEP    
-DFNDELAY=O_NDELAY            -o chat.o chat.c
cc -o chat chat.o
make[1]: Leaving directory `/home/ian/ppp-2.3.9/chat'
cd pppd; make  all
make[1]: Entering directory `/home/ian/ppp-2.3.9/pppd'
cc -O2 -pipe -Wall -g -D_linux_=1 -DHAVE_PATHS_H -DIPX_CHANGE
main.c -o main.o
In file included from /usr/include/sys/resource.h:27, from main.c:39:
/usr/include/resourcebits.h:103: warning: `RLIM_INFINITY' redefined
/usr/include/asm/resource.h:25: warning: this is the location of the
previous definition
In file included from /usr/include/sys/resource.h:27, from main.c:39:
/usr/include/resourcebits.h:102: parse error before `('
make[1]: *** [main.o] Error 1
make[1]: Leaving directory `/home/ian/ppp-2.3.9/pppd'
make: *** [all] Error 2

It seems to be having a problem with resource.h which I beleive is a
part of the GNU C library (?)  Could this mean that I have outdated C
libraries ? Is there a way of checking which versions I have ?



PS: 2.3.40 kernel (upgraded from 2.0.36)


strange compile error with pppd

Post by Ian Mortime » Tue, 25 Jan 2000 04:00:00

NoMadis wrote some stuff here......

Quote:> 2.2.14. The 2.3.xx range is the unstable developers version, and one is
> bound to run into all kinds of strange errors.
> When you run an unstable kernel you are supposed to know what you are


Quote:> doing :))

That's a rather elitist view isn't it ? :)

As long as I don't pester the group with too many dumbass questions
(like this one) then there's nothing wrong with diving head first into
the "good stuff" now and again !

Anyway, my box runs absolutely fine at the moment (just a few changes to
the aha152x scsi driver and a few other tweaks had it running in no time
!) - just this little problem with pppd (which isn't a fault of the
kernel really - pppd 2.3.5 doesn't support the new kernel driver like
2.3.9 can)

Thanks for the advice - I'll check my libraries and see what 2.2.14 can
do for me tomorrow.

See Ya


> --
> Greetz,
> Joop
> -----------------------------------------------------------------------
>  Joop Bollen.   Nuts & Bolts Department,    Nomadis Systems, Holland

> We all live under the same sky, but we don't all have the same horizon.


1. Compiling pppd with cbcp (was Re: can't compile pppd)

Good idea - I've now done that. Infact I've even re-installed the whole
OS too, so its now at RH 5.0.

Well, no. I didn't realise there was a version of 2.2.0g with MSCHAP
compiled into it at the time. Anyway, the current situation is like

I've got ppp-2.3.3 (both src and binary RPMs). I've made the assumption
that MSCHAP and call back aren't compiled in by default, and have tried
compiling my own version. The README.MSCHAP80 and README.cbcp files are
very straightforward, and I compiled pppd with MSCHAP support without a

As for the callback, when I patch the ./pppd/Makefile.linux file
according to the instructions, I get success almost all the way there,
and then;

-DCHAPMS=1 -DUSE_CRYPT=1   -c cbcp.c -o cbcp.o
cbcp.c:50: `PPP_CBCP' undeclared here (not in a function)
cbcp.c:50: initializer element for `cbcp_protent.protocol' is not
cbcp.c: In function `cbcp_send':
cbcp.c:380: `PPP_CBCP' undeclared (first use this function)
cbcp.c:380: (Each undeclared identifier is reported only once
cbcp.c:380: for each function it appears in.)
make: *** [cbcp.o] Error 1

When I read the patch that is supposed to update the Makefile to enable
call back, I noticed that the Makefile appears to have changed slightly
since the patch was built (a couple of line numbers are out of sync).

I've never applied a patch before, so I decided to just edit the
Makefile myself. There are only two changes to be made, so I'm confident
I didn't make a balls of it.

I think that the patch was made at version 2.3.0, and I'm trying to
apply it to 2.3.3. I may be talking out of my backside though.
Suggestions, anybody? Please... I'm getting seriously frustrated by this
now, and refuse to revert to Win95. I shan't, I shan't, I shan't....

An easy question - does the binary RPM available from Red Hat's contrib
directory at their ftp site support dial back and MSCHAP by default? I
havn't even considered this possibility, and will be as sick as a pig
(and rather relieved) if it does...

Yes, Red Hat defaults to PPP support via a module. Allegedly.

Thanks for the info.


2. Basic pnp modem question...

3. OpenSuse 11.1 Kinternet error: "pppd[0] died: pppd options error (exit code 2)

4. DDS3 reading on a 4GB drive

5. Strange pppd error

6. Expiration of Netscape Navigator

7. PPPD Compile errors

8. proute2 source code / package ?

9. pppd 2.3.3 compile error using HAS_SHADOW=1

10. pppd 2.3.4 compile error

11. pppd 2.3.5 compile error under RH5.1

12. pppd 2.3.3 compile error using HAS_SHADOW=1

13. pppd - need help compiling pppd 2.2.0f