Problems compiling - gcc Command line arguments

Albert E. Whale aewhale@access.hky.com
Thu Dec 30 05:51:00 GMT 1999


I have tried many different locations before posting here.  But this
seems to be the location where my answers will most likely come from.

I am currently involved in a Migration Project.  When I am compiling the
source code, I am getting the following Warning statements which appear
incocluous, but also prohibit the compilation process.

What is important to note here, is that there are no errors in the
software whenever it is compiled on a Non-Linux box.  What command line
options can I provide to the gcc compiler to reduce the number of
warnings and get it to behave more like other compilers?


fxscrf.c:247: warning: `scr_alloc' was declared implicitly `extern' and
later `s
tatic'
fxscrf.c:123: warning: previous declaration of `scr_alloc'
fxscrf.c:269: warning: `scr_free' was declared implicitly `extern' and
later `st
atic'
fxscrf.c:221: warning: previous declaration of `scr_free'
fxscrf.c:279: warning: `sub_alloc' was declared implicitly `extern' and
later `s
tatic'
fxscrf.c:186: warning: previous declaration of `sub_alloc'
fxscrf.c:336: warning: `sub_free' was declared implicitly `extern' and
later `st
atic'
fxscrf.c:188: warning: previous declaration of `sub_free'
fxscrf.c:371: warning: `setrownum' was declared implicitly `extern' and
later `s
tatic'
fxscrf.c:262: warning: previous declaration of `setrownum'
fxscrf.c:411: warning: `setslist' was declared implicitly `extern' and
later `st
atic'

-- 
Albert E. Whale       aewhale@hky.com
http://www.hky.com/aewhale.html
------------------------------------------------------------------
Sr. Database, Internet and Unix Systems Consultant

Pennsylvania Parenthood Initiative - It takes two people to become
parents, the children need both of them!
http://www.geocities.com/Heartland/4688/papi.htm
Parents without Partners - Past President
Co-Founder of The Purple Heart Foundation


More information about the Gcc mailing list