SIOCSIFADDR: Invalid argument

Sergey Ostrovsky sostrovsky at snip.net
Tue Dec 19 19:45:13 PST 2000


ken_i_m wrote:

> At 09:59 PM 12/19/00 -0500, you wrote:
> >What king of "ugly errors" are you exactly getting? Paste the output, maybe
> >someone can help you.
>
> Here is a ~20 line head output:
>
> (cd  inetd && make)
> make[1]: Entering directory `/usr/src/netkit-base-0.17/inetd'
> gcc -O3 -march=i686 -O2 -Wall -W -Wpointer-arith -Wbad-function-cast
> -Wcast-qual -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations
> -Wnested-externs -Winline  inetd.c -c
> In file included from /usr/include/string.h:346,
>                   from /usr/include/sys/un.h:24,
>                   from inetd.c:125:
> /usr/include/bits/string2.h: In function `__strcpy_small':
> /usr/include/bits/string2.h:419: warning: pointer of type `void *' used in
> arithmetic
> /usr/include/bits/string2.h:427: warning: pointer of type `void *' used in
> arithmetic
> /usr/include/bits/string2.h:432: warning: pointer of type `void *' used in
> arithmetic
> /usr/include/bits/string2.h:437: warning: pointer of type `void *' used in
> arithmetic
> /usr/include/bits/string2.h:439: warning: pointer of type `void *' used in
> arithmetic
> /usr/include/bits/string2.h:444: warning: pointer of type `void *' used in
> arithmetic
> inetd.c: In function `exec_child':
> inetd.c:380: warning: comparison between signed and unsigned
> inetd.c: In function `bump_nofile':
> inetd.c:1026: warning: comparison between signed and unsigned
> gcc -O3 -march=i686 -O2 -Wall -W -Wpointer-arith -Wbad-function-cast
> -Wcast-qual -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations
> -Wnested-externs -Winline  servtab.c -c
> In file included from /usr/include/string.h:346,
>                   from /usr/include/sys/un.h:24,
>
> I think, therefore, ken_i_m
>
> --
> Unsubscribe: send email to lfs-discuss-request at linuxfromscratch.org
> and put unsubscribe in the subject header of the message

About "warning: pointer of type `void *' used in arithmetic"
1. These are warnings ( sly thing knows it should be taken as char* )
2. If if _really_ bothers you, it is better not to work with glibc-2.2, because

    you will see screenfuls of this.
3. Aside of esthetic feelings ( BTW, I do not enjoy seeing this crap also ),
it's harmless.

Sergey Ostrovsky.



-- 
Unsubscribe: send email to lfs-discuss-request at linuxfromscratch.org
and put unsubscribe in the subject header of the message




More information about the lfs-dev mailing list