On Mon, Jun 14, 1999 at 09:32:40PM +0100, Rupert Heesom wrote:
> At 04:35 PM 6/13/99 , Gyepi SAM wrote:
> >In my version version of diald, .98.2, diald.h includes both files; the
> >linux version if GLIBC is defined, the inet version otherwise.
> 
> Where do you get version 98.2 from?   When I visit the DialD web site, it
> says the latest version is 0.16 which is I assume what I'm trying to compile.

        http://filewatcher.org

> 
> >
> >It is hardly wise to delete or move directories to avoid this problem
> >unless you know what you are doing.  The problem usually gets worse.
> >
> >To create a link to the linux include directory
> >     
> >     cd /usr/include; rm linux; ln -s /usr/src/linux/include linux
> 
> Thanks for this, I recreated the link, now the files are back to what they
> were, and I'm getting the same old error msgs back again.   Since I don't
> yet know how to capture the screen output, I will type in here what I got
> from a couple of the last lines of output.  All the msgs are basically the
> same; just the vars (bits in "") are different:
> 
> /usr/include/linux/in.h: 114: warning: "INADDR_UNSPEC_GROUP" redefined
> /usr/include/netinet/in.h: 140:  warning:  this is the location of the
> previous definition.

No, no, include the actual error messages.  There's a lot of info hidden
in the compiler error logs.  Run make in a window like this

        make &> diald_errors

while doing 
        
        tail -f diald_errors

in another window.

if you want to run the whole thing in one window, do

        touch diald_errors; tail -f diald_errors; make &> diald_errors

At the end, post the contents of diald_errors.

> 
> >
> >There should be two or three other such links into the kernel source.
> >
> >     less /usr/src/linux/README
> 
> I tried doing the above line; there didn't seem to be a README file in the
> /usr/src/linux-2.0.36/include/linux directory.
> 

There isn't.  Try /usr/src/linux/README


> 
> >Gcc normally knows to get header files from /usr/include 
> >unless it has been configured otherwise.  You should not have to give it
> >that information, but you can add 
> >
> >     -I/usr/include
> >
> >to the CFLAGS line of the Makefile as a temporary fix.  
> 
> 
> I also tried the "-l/usr/include" bit at the end of the "CFLAGS" line in
> the Makefile file.  Didn't seem to help.

This is ineffective.  There are no libraries in /usr/include.  Unless
you put them there, which would be a mistake.  The -l flag is used with
a directory that contains libraries.  
[snip]
 
> Hope you can help some more.   Linux challenges never seem to end!   Once
> this compiles OK, is there any guarantee that the next prog I have to
> compile will work OK?

Nope. Never any guarantees, but most work.


-Gyepi


> 
> Regards
> rupert.
> 
> 
> ----------------------------------------------------------------------------
> --------------------------------------
> Yesterday it worked               Remember: Windows is not the answer - 
> Today it is not working           Windows is the question and the answer is
> no...
> Windows is like that.
> 
> 
> 
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-diald" in
> the body of a message to [EMAIL PROTECTED]
> 

-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]

Reply via email to