Hi!

Compiler version: gcc (GCC) 4.1.0 20060304 (Red Hat 4.1.0-3)

I was trying to build libraries from source given by a module that I will hooked up to my host computer. The build process kept being terminated everytime warnings are being found.

How do I bypass the warnings and continue compiling? I really need to build this library to develope my program.

Thanks.

the option -Werror makes warnings into errors.. check to see if the makefile your program is using is using this option..

maybe you should look into the errors.. if they have -Werror turned on then they are expecting no warnings..

How do I go around checking for the flag. Is there a command that I can use to disable that warning error flag? I typed in the -Wno-error command but it didn't work. Am I missing something here?
I checked the makefile. Nothing indicates that the Werror flag is set or anything of that sort.

I'm new at gcc. If you don't mind, can you please guide me through step by step?

Thank you for your time.

Hi -

"-Werror" is a guess on our part.

Please post the actual error message, and the corresponding "gcc" compile command. That will help us determine the actual problem, and the recommended solution.

Thanx in advance .. PSM

I managed to bypass each errors by debugging the codes but it gets messier and very troublesome.


Warnings that are treated as errors:
+++++++++++++++++++++++++++++++++++++++++++++++++++++++
cc1plus: warnings being treated as errors
aGarciaAgent/acpGarciaAgent.cpp: In member function ‘void acpGarciaAgent::doRead()’:
aGarciaAgent/acpGarciaAgent.cpp:535: warning: dereferencing type-punned pointer will break strict-aliasing rules
make[2]: *** [unix_aGarciaAgent_Data/i686/aRelease/acpGarciaAgent.op] Error 1
make[2]: Leaving directory `/root/Desktop/brainstem/aGarcia'
make[1]: *** [release] Error 2
make[1]: Leaving directory `/root/Desktop/brainstem/aGarcia'
make: *** [release] Error 2
+++++++++++++++++++++++++++++++++++++++++++++++++++++++


Next warning which is similar to previous one.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++
cc1plus: warnings being treated as errors
../aCommon/acpPkgImport.cpp: In member function ‘acpPackageTag* acpPkgImport::getNamedTag(const char*)’:
../aCommon/acpPkgImport.cpp:167: warning: dereferencing type-punned pointer will break strict-aliasing rules
make[2]: *** [unix_aRobotPackager_Data/i686/aRelease/acpPkgImport.op] Error 1
make[2]: Leaving directory `/root/Desktop/brainstem/aRobot'
make[1]: *** [release] Error 2
make[1]: Leaving directory `/root/Desktop/brainstem/aRobot'
make: *** [release] Error 2
+++++++++++++++++++++++++++++++++++++++++++++++++++++++

Next warning:

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
cc1plus: warnings being treated as errors
aCommon/aConsole.c: In function ‘aErr aConsole_Initialize(aConsole*)’:
aCommon/aConsole.c:245: warning: ‘licenseErr’ may be used uninitialized in this function
make[2]: *** [unix_aConsole_Data/i686/aRelease/aConsole.o] Error 1
make[2]: Leaving directory `/root/Desktop/brainstem/aConsole'
make[1]: *** [release] Error 2
make[1]: Leaving directory `/root/Desktop/brainstem/aConsole'
make: *** [release] Error 2
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


Again thank you for your time.

OK - your output indicates that xhi's hunch about "-Werror" is absolutely correct:It also indicates that you don't just have *one* makefile: you have a whole bunch of them (one in each subdirectory). And quite probably some kind of "config" file in the root directory.

Soooo ....

I'd suggest the following:
1. See if you can "grep" for "-Werror" in any of your Makefiles, or some config file. Start at the root directory of your source tree.

When you find it, simply modify the file, run "make clean", and re-run "make all" to rebuild everything.

If that doesn't work, then:

2. See if you can grep for a "gcc", "gcc" or "CFLAGS" option in any of these makefiles.

If that still doesn't work:

3. It looks like the main page for the project you're trying to build is here:

http://www.easierrobotics.com/

You might be able to post your question to a discussion group there.

'Hope that helps .. PSM

This is the only file I found that has CFLAGS

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

# makefile: host/aTEAvm/aCommon

ROOT = ../../

INCLUDES = \
-I. \
-I../aUnix \
-I../../aCommon \
-I ../../aIO/aCommon \
-I ../../aIO/aUnix \
-I ../../aStem/aCommon \
-I ../../aStem/aUnix \
-I ../../aSteep/aCommon \
-I ../../aTEAvm/aCommon

OBJECTDIR = ../unix_aTEAvm_Data

SOURCE = ../../aCommon/aAssert.c \
../../aCommon/aMemPool.c \
../../aCommon/aMemHandleDebug.c \
../../aCommon/aMemLeakDebug.c \
aSteepOpt.c \
aSteepOptInternal.c

CFLAGS = -Wall -DaUNIX -c -fPIC

# include the generic file for all object building
include $(ROOT)object_makefile


+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Do I replace
CFLAGS = -Wall -DaUNIX -c -fPIC
with
CFLAGS = -Wno-error -DaUNIX -c -fPIC
?

Thanks.

No, smallfire - you still haven't found the place where "-Werror" is being set. "-Wall" isn't equivalent to "-Werror", and the source in question is for "C" modules, but your compiler errors are occurring on "C++" modules.

Try the forums on http://www.easierrobotics.com/

Or "grep" *everything* in your top-level directories for "Werror"
EXAMPLE:

Thank you, paulsm4, for being really patient with me.

I ran it. I didn't know Linux well enough to use that grep command line. Sorry about that. I was using the typical search for matching words through the whole directory. FYI, I tried the forum on http://www.easierrobotics.com/ but I haven't gotten any reply so far. I need this up and running asap. That is why I approach linuxquestions.org instead.

Now, these must be all the flags we are looking for.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++
[root@d-15-31 ~]# grep Werror * */* */*/* 2> /dev/null
Desktop/brainstem/make_library.Linux: @$(CC) -gfull -shared -Wall -Werror \
Desktop/brainstem/make_library.Linux: @$(CC) -shared -Wall -Werror \
Desktop/brainstem/make_program_cpp.LinuxBGCFLAGS := -include aUnix/unix_$(PROG NAME)_pfxd.h -Wall -Werror \
Desktop/brainstem/make_program_cpp.Linux:RELCFLAGS := -include aUnix/unix_$(PROG NAME)_pfx.h -Wall -Werror \
Desktop/brainstem/make_program_cpp.Linux: @$(CCP) -gfull -Wall -Werror -Wl ,-rpath ./ \
Desktop/brainstem/make_program_cpp.Linux: @$(CCP) -Wall -Werror -Wl,-rpath ./ \
Desktop/brainstem/make_program.LinuxBGCFLAGS := -include aUnix/unix_$(PROGNAME )_pfxd.h -Wall -Werror \
Desktop/brainstem/make_program.Linux:RELCFLAGS := -include aUnix/unix_$(PROGNAME )_pfx.h -Wall -Werror \
Desktop/brainstem/make_program.Linux: @$(CC) -g -Wall -Werror -Wl,-rpath ./ -L $(DBGOUTDIR) $(LIBRARIES) \
Desktop/brainstem/make_program.Linux: -Wall -Werror -Wl,-rpath ./ -L$(RE LOUTDIR) $(LIBRARIES) \

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
What do I do next? Modify all the @$(CC) to exclude -Werror? -Wno-error?


For example:
@$(CC) -gfull -shared -Wall -Werror
replaced by
@$(CC) -gfull -shared -Wall
?

or
@$(CC) -gfull -shared -Wall -Wno-error
?
++++++

I found some explanation/references regarding gcc commands etc but using the command correctly is another whole new story. Do you know of any good references? Or is it a learn-through-experience type of knowledge?

Again and again, thank you for your time.

Finally, it compiled smoothly. Thanks.

Hi, smallfire -

Sorry I wasn't able to be more help, but different packages often have (very!) different build procedures, so it can be difficult to give you the right advice.

Nevertheless, it sounds like you did exactly the right thing - and I'm glad it worked for you!

Congratulations - and good job!

Sincerely .. PSM

there are a *lot* of options for gcc. some are used often and others are not. one way to see what are common options is to build as much as possible from source, and while it is building pay attention to the flags that are used to compile. then check out those options in the docs for gcc.. there is alot of docs at the gcc website..

and yes experience is a big part.. but again i would suggest building everything possible from source, not only will it enlighten you as to how things are built, but it will also teach you alot about your system and software in general..

Thanks again for all the guidance.
I have a great time learning!

+++++++++++++
I assume I can start developing my program now and compile via gcc -o outputfilename -I"PATH/to/the/include/files" inputfile.c

I need to enable permission for the serial port.
How do I do it?
I found /dev/ttyS0 (ttyS1) in other threads. I tried and it said "permission denied". Is there another flag that I need to set? I'm planning to write a makefile for compiling my programs. Should I be including the serial port permission in the makefile or is it a one time setting? I know that the serial port permission is disabled by default.
+++++++++++++