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.
>
>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.
>
>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.
>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.
>
>BTW, we are talking about header files, not libraries. Header files
>contain declarations and other pieces of information necessary for the
>compiler to do it's job. Libraries contain object code (for the
>declared functions and variables) which the linker links to your object
>files (once you get it to compile). They are quite different creatures.
I'm not entirely sure what you're saying above, but perhaps I'll learn in
time.
>
>If you are still having trouble, post the offending lines from the
>compiler and tell us what system you are running and which version of
>diald you are using.
Well as far as I know, I'm using Kernel 2.0.36 with the RH5.2 distribution,
and Diald 0.16 as mentioned above.
Certainly the readme file that came with the Diald download talks of
version 0.16. Since I've come across the directory "linux-2.0.36" I
assume that I'm right in assuming that is the version of the kernel.
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?
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]
