Problem using apgcc in with Ubuntu 9.04

[Gustavo Serra]

Hi.

First of all, sorry if this subject has already been dealt with, I
haven't found any information. Using APBUILD_DEBUG=1 I realized that
-U_FORTIFY_SOURCE is used to compile my sources. However, this flag
seem to disable the options -Wall and -Werror (compiling with gcc
instead of apgcc, I get the new gcc 4.3 warnings about unused return
values):

# /usr/bin/gcc -I/usr/local/include/apbuild -include
/usr/local/include/apbuild/apsymbols.h -DAPBUILD_VERSION="2.0.9"
-fno-stack-protector -U_FORTIFY_SOURCE pdvio.c -pipe -pthread -Wall
-Werror -O2 -fPIC -I../include -march=i486 -c -o .obj/release/pdvio.o

If I run the line above manually and remove the -U flag, I get all the warnings.
I can edit apgcc and remove this flag, but I am unaware of the consequences.

Also, I had to edit apsymbols.h and replace @GLIBC_2.2.5 for
@GLIBC_2.3. Otherwise I would get these errors:

$ make
apgcc -pipe -pthread -Wall -Werror -O2 -fPIC -I../include
-march=i486 -c -o .obj/release/pdvio.o pdvio.c
{standard input}: Assembler messages:
{standard input}:26: Error: multiple versions
[`***@GLIBC_2.3'|`***@GLIBC_2.2.5'] for symbol
`sys_errlist'
{standard input}:27: Error: multiple versions
[`***@GLIBC_2.2.5'|`***@GLIBC_2.3'] for symbol
`_sys_errlist'
{standard input}:28: Error: multiple versions
[`***@GLIBC_2.3'|`***@GLIBC_2.2.5'] for symbol `sys_nerr'
{standard input}:29: Error: multiple versions
[`***@GLIBC_2.2.5'|`***@GLIBC_2.3'] for symbol `_sys_nerr'

What is the correct manner to deal with these problems?
Thanks any advice.

---------------------------------------------------------------------
To unsubscribe, e-mail: autopackage-dev-unsubscribe-OfajU3CKLf1/***@public.gmane.org
For additional commands, e-mail: autopackage-dev-help-OfajU3CKLf1/***@public.gmane.org

[Jan Niklas Hasse]

On Wed, Jun 10, 2009 at 10:34 PM, Gustavo

Post by Gustavo Serra
Hi.
First of all, sorry if this subject has already been dealt with, I
haven't found any information. Using APBUILD_DEBUG=1 I realized that
-U_FORTIFY_SOURCE is used to compile my sources. However, this flag
seem to disable the options -Wall and -Werror (compiling with gcc
instead of apgcc, I get the new gcc 4.3 warnings about unused return
# /usr/bin/gcc -I/usr/local/include/apbuild -include
/usr/local/include/apbuild/apsymbols.h -DAPBUILD_VERSION="2.0.9"
-fno-stack-protector -U_FORTIFY_SOURCE pdvio.c -pipe -pthread -Wall
-Werror -O2 -fPIC -I../include -march=i486 -c -o .obj/release/pdvio.o
If I run the line above manually and remove the -U flag, I get all the warnings.
I can edit apgcc and remove this flag, but I am unaware of the consequences.

AFAIK the source fortifying (don't know how to call that thing, but it
can be turned off by -U_FORTIFY_SOURCE) was introduced in glibc 2.7.
Therefore we added the flag.
You normally don't want to see the warnings anyway because apbuild
should only be used to build binaries which will be distributed.

Post by Gustavo Serra
$ make
apgcc -pipe -pthread -Wall -Werror   -O2 -fPIC  -I../include
-march=i486 -c -o .obj/release/pdvio.o pdvio.c
{standard input}:26: Error: multiple versions
`sys_errlist'
{standard input}:27: Error: multiple versions
`_sys_errlist'
{standard input}:28: Error: multiple versions
{standard input}:29: Error: multiple versions
What is the correct manner to deal with these problems?

This one looks like a bug/problem by apgcc's apsymbols.h file. I think
it can only be fixed if we let apgcc run the buildlist script before
compiling. I will try to implement something in the next days.

---------------------------------------------------------------------
To unsubscribe, e-mail: autopackage-dev-unsubscribe-OfajU3CKLf1/***@public.gmane.org
For additional commands, e-mail: autopackage-dev-help-OfajU3CKLf1/***@public.gmane.org

[Gustavo Serra]

Thanks for the quick answer. I am at your disposal if testing or more
details are necessary.

Post by Jan Niklas Hasse
On Wed, Jun 10, 2009 at 10:34 PM, Gustavo

Post by Gustavo Serra
Hi.
First of all, sorry if this subject has already been dealt with, I
haven't found any information. Using APBUILD_DEBUG=1 I realized that
-U_FORTIFY_SOURCE is used to compile my sources. However, this flag
seem to disable the options -Wall and -Werror (compiling with gcc
instead of apgcc, I get the new gcc 4.3 warnings about unused return
# /usr/bin/gcc -I/usr/local/include/apbuild -include
/usr/local/include/apbuild/apsymbols.h -DAPBUILD_VERSION="2.0.9"
-fno-stack-protector -U_FORTIFY_SOURCE pdvio.c -pipe -pthread -Wall
-Werror -O2 -fPIC -I../include -march=i486 -c -o .obj/release/pdvio.o
If I run the line above manually and remove the -U flag, I get all the warnings.
I can edit apgcc and remove this flag, but I am unaware of the consequences.

AFAIK the source fortifying (don't know how to call that thing, but it
can be turned off by -U_FORTIFY_SOURCE) was introduced in glibc 2.7.
Therefore we added the flag.
You normally don't want to see the warnings anyway because apbuild
should only be used to build binaries which will be distributed.

Post by Gustavo Serra
$ make
apgcc -pipe -pthread -Wall -Werror   -O2 -fPIC  -I../include
-march=i486 -c -o .obj/release/pdvio.o pdvio.c
{standard input}:26: Error: multiple versions
`sys_errlist'
{standard input}:27: Error: multiple versions
`_sys_errlist'
{standard input}:28: Error: multiple versions
{standard input}:29: Error: multiple versions
What is the correct manner to deal with these problems?

This one looks like a bug/problem by apgcc's apsymbols.h file. I think
it can only be fixed if we let apgcc run the buildlist script before
compiling. I will try to implement something in the next days.
---------------------------------------------------------------------

---------------------------------------------------------------------
To unsubscribe, e-mail: autopackage-dev-unsubscribe-OfajU3CKLf1/***@public.gmane.org
For additional commands, e-mail: autopackage-dev-help-OfajU3CKLf1/***@public.gmane.org

[Jan Niklas Hasse]

On Wed, Jun 10, 2009 at 11:22 PM, Gustavo Serra <

Post by Gustavo Serra
Thanks for the quick answer. I am at your disposal if testing or more
details are necessary.

Great! I could need some more testing concerning this beta build of apbuild
2.1.0:
http://watteimdocht.de/autopackage/Autopackage Development Environment
1.4.2.package

You might also have a look at my other email on the mailing list.