Hi all,
I was just installing the 44R16 release and noticed a lot of warnings
during compilation. As an example:
/usr/include/features.h:184:3: warning: #warning "_BSD_SOURCE and
_SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
Just changing the "_BSD_SOURCE" for "_DEFAULT_SOURCE" in
'Makefile.config' reduced a lot the number of warnings. Other warnings
still are issued though.
Some of us are sort of development savvy and could (perhaps) use some
time to try to fix those warnings. They are possibly harmless most of
the time, but their meaning is that the software can have some weakness.
Wouldn't be interesting to incentive whoever are interested to try to
fix those?
By the way, GCC is becoming more and more picky about many things,
that is, it is evolving. Some things that were treated as a warning
or even accepted are being flagged as error these days. I got some of
these in FreeUSP compiling recently and I am having an error in
compilation of sfio/segdread:
cc -c -I. -I.. -O -Dvt_threaded=0 stdfgetc.c
In file included from /usr/include/wchar.h:43:0,
from ../sfhdr.h:304,
from stdio_s.h:11,
from stdfgetc.c:1:
/usr/include/x86_64-linux-gnu/bits/types/__FILE.h:5:25: error:
conflicting types for ‘__FILE’ typedef struct _IO_FILE __FILE;
^~~~~~
In file included from stdfgetc.c:1:0:
stdio_s.h:8:25: note: previous declaration of ‘__FILE’ was here
typedef struct _sfio_s *__FILE;
^~~~~~
Makefile:25: recipe for target 'stdfgetc.o' failed
make[5]: *** [stdfgetc.o] Error 1
I will try to dig it.
Best regards.
Roxo
--
---------------- Non luctari, ludare -------------------+ WYSIWYG
Fernando M. Roxo da Motta <petro@roxo.org> | Editor?
Except where explicitly stated I speak on my own behalf.| VI !!
PU5RXO | I see text,
------------ Quis custodiet ipsos custodes?-------------+ I get text!
_______________________________________________
Seisunix mailing list
Seisunix@mailman.seismic-unix.org
https://mailman.seismic-unix.org/listinfo/seisunix