Your message dated Wed, 23 Dec 2015 19:49:20 -0700 (MST)
with message-id <[email protected]>
and subject line fixed a while ago
has caused the Debian Bug report #746174,
regarding Conflicting declarations of ao_symbols
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
746174: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746174
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: altos
Version: 1.3.2-1
Usertags: goto-cc

While compiling the package using our research compiler infrastructure the build
failed with the following error:

[...]
libtool: link: gcc -I../../ao-tools/lib -I/usr/include/libusb-1.0 -g -o ao-load 
ao-load.o  ../../ao-tools/lib/libao-tools.a -lusb-1.0
error: conflicting types for variable "ao_symbols"
old definition in module ao-load file ao-load.c line 33
struct sym [3l]
new definition in module ao-editaltos file ao-editaltos.h line 25
struct ao_sym [5l]
make[4]: *** [ao-load] Error 64

Looking at the source, the following indeed conflict:

http://sources.debian.net/src/altos/1.3.2-1/ao-tools/ao-load/ao-load.c?hl=29,30,31,32,33#L29

vs.

http://sources.debian.net/src/altos/1.3.2-1/ao-tools/lib/ao-editaltos.c?hl=22#L22
using the definition of struct ao_sym from here:
http://sources.debian.net/src/altos/1.3.2-1/ao-tools/lib/ao-hex.h?hl=52,53,54,55,56,57,58#L52

(Note that the build does FTFBS with the standard compiler, as no type checking
at link time would be performed.)

Best,
Michael

Attachment: pgpFOGPmy4fJH.pgp
Description: PGP signature


--- End Message ---
--- Begin Message ---
This was fixed a while ago, just forgot to close the Debian bug.

Bdale

--- End Message ---

Reply via email to