4.6 compile messages: Do I have to worry?

View: New views
2 Messages — Rating Filter:   Alert me  

4.6 compile messages: Do I have to worry?

by Toni Mueller-12 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi,

today I compiled 4.6-stable from source on an amd64 machine, and got a
lot of error messages like this (sample):

About 20 or so of these:

lint -hx  -I/usr/src/lib/libm/arch/amd64 -I/usr/src/lib/libm/src -I/usr/src/lib/libm/src/ld80 -i /usr/src/lib/libm/src/s_conj.c
/usr/include/complex.h:43: syntax error
/usr/include/complex.h:44: syntax error
/usr/include/complex.h:45: syntax error
/usr/include/complex.h:46: syntax error
/usr/include/complex.h:47: syntax error



And about 5 or so of these:

lint -hx -DL_ENDIAN -DDSO_DLFCN -DHAVE_DLFCN_H -DTERMIOS -DANSI_SOURCE -DNO_ERR -DNO_WINDOWS_BRAINDEATH -DOPENSSL_NO_IDEA -DOPENSSL_NO_RC5 -DOPENSSL_NO_KRB5 -DOPENSSL_NO_MDC2 -DOPENSSL_NO_HW_4758_CCA -DOPENSSL_NO_HW_AEP -DOPENSSL_NO_HW_ATALLA -DOPENSSL_NO_CAPIENG -DOPENSSL_NO_HW_CSWIFT -DOPENSSL_NO_HW_NCIPHER -DOPENSSL_NO_HW_NURON -DOPENSSL_NO_HW_PADLOCK -DOPENSSL_NO_HW_SUREWARE -DOPENSSL_NO_HW_UBSEC -I/usr/src/lib/libssl/crypto/../src -I/usr/src/lib/libssl/crypto/../src/crypto -I/usr/src/lib/libssl/crypto/obj -DMD5_ASM -DSHA1_ASM -DOPENSSL_CPUID_OBJ  -i /usr/src/lib/libssl/crypto/../src/crypto/bn/asm/x86_64-gcc.c
/usr/src/lib/libssl/src/crypto/bn/asm/x86_64-gcc.c:108: syntax error
/usr/src/lib/libssl/src/crypto/bn/asm/x86_64-gcc.c:108: syntax error
/usr/src/lib/libssl/src/crypto/bn/asm/x86_64-gcc.c:108: syntax error
/usr/src/lib/libssl/src/crypto/bn/asm/x86_64-gcc.c:108: warning: high may be used before set
/usr/src/lib/libssl/src/crypto/bn/asm/x86_64-gcc.c:109: syntax error
/usr/src/lib/libssl/src/crypto/bn/asm/x86_64-gcc.c:109: syntax error
/usr/src/lib/libssl/src/crypto/bn/asm/x86_64-gcc.c:109: cannot recover from previous errors


The compile appears to complete ok, but these messages don't seem right
to me. But then, they're "only" lint messages...


TIA!



Kind regards,
--Toni++


Re: 4.6 compile messages: Do I have to worry?

by Jonathan Gray :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Sat, Oct 24, 2009 at 05:51:28PM +0200, Toni Mueller wrote:

> Hi,
>
> today I compiled 4.6-stable from source on an amd64 machine, and got a
> lot of error messages like this (sample):
>
> About 20 or so of these:
>
> lint -hx  -I/usr/src/lib/libm/arch/amd64 -I/usr/src/lib/libm/src -I/usr/src/lib/libm/src/ld80 -i /usr/src/lib/libm/src/s_conj.c
> /usr/include/complex.h:43: syntax error
> /usr/include/complex.h:44: syntax error
> /usr/include/complex.h:45: syntax error
> /usr/include/complex.h:46: syntax error
> /usr/include/complex.h:47: syntax error
>
>
>
> And about 5 or so of these:
>
> lint -hx -DL_ENDIAN -DDSO_DLFCN -DHAVE_DLFCN_H -DTERMIOS -DANSI_SOURCE -DNO_ERR -DNO_WINDOWS_BRAINDEATH -DOPENSSL_NO_IDEA -DOPENSSL_NO_RC5 -DOPENSSL_NO_KRB5 -DOPENSSL_NO_MDC2 -DOPENSSL_NO_HW_4758_CCA -DOPENSSL_NO_HW_AEP -DOPENSSL_NO_HW_ATALLA -DOPENSSL_NO_CAPIENG -DOPENSSL_NO_HW_CSWIFT -DOPENSSL_NO_HW_NCIPHER -DOPENSSL_NO_HW_NURON -DOPENSSL_NO_HW_PADLOCK -DOPENSSL_NO_HW_SUREWARE -DOPENSSL_NO_HW_UBSEC -I/usr/src/lib/libssl/crypto/../src -I/usr/src/lib/libssl/crypto/../src/crypto -I/usr/src/lib/libssl/crypto/obj -DMD5_ASM -DSHA1_ASM -DOPENSSL_CPUID_OBJ  -i /usr/src/lib/libssl/crypto/../src/crypto/bn/asm/x86_64-gcc.c
> /usr/src/lib/libssl/src/crypto/bn/asm/x86_64-gcc.c:108: syntax error
> /usr/src/lib/libssl/src/crypto/bn/asm/x86_64-gcc.c:108: syntax error
> /usr/src/lib/libssl/src/crypto/bn/asm/x86_64-gcc.c:108: syntax error
> /usr/src/lib/libssl/src/crypto/bn/asm/x86_64-gcc.c:108: warning: high may be used before set
> /usr/src/lib/libssl/src/crypto/bn/asm/x86_64-gcc.c:109: syntax error
> /usr/src/lib/libssl/src/crypto/bn/asm/x86_64-gcc.c:109: syntax error
> /usr/src/lib/libssl/src/crypto/bn/asm/x86_64-gcc.c:109: cannot recover from previous errors
>
>
> The compile appears to complete ok, but these messages don't seem right
> to me. But then, they're "only" lint messages...

lint does not yet understand all of C99, ie complex types.
These warnings are harmless, hopefully lint will be updated
to cope with reality in the future.