[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#768484: marked as done (libiberty-dev conflicts with binutils-dev re ansidecl.h)



Your message dated Tue, 20 Dec 2016 12:20:22 +0100
with message-id <115eb7c7-2cd5-d340-9978-b97c1f6bf73a@debian.org>
and subject line Re: libiberty-dev conflicts with binutils-dev re ansidecl.h
has caused the Debian Bug report #768484,
regarding libiberty-dev conflicts with binutils-dev re ansidecl.h
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 owner@bugs.debian.org
immediately.)


-- 
768484: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768484
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: libiberty-dev
Version: 20131116-1

Both binutils-dev and libiberty-dev include the file "ansidecl.h"

dpkg -S ansidecl.h
binutils-dev: /usr/include/ansidecl.h
libiberty-dev:amd64: /usr/include/libiberty/ansidecl.h

Both use the standard header protection mechanism:

#ifndef _ANSIDECL_H
#define _ANSIDECL_H 1

thus only one of the two can ever get included.

Only /usr/include/libiberty/ansidecl.h defines
ATTRIBUTE_RETURNS_NONNULL ATTRIBUTE_SENTINEL ATTRIBUTE_MALLOC
ATTRIBUTE_NORETURN
and so on ... Thus, making use of libiberty.h will cause a build
break, because these are not defined when the ansidecl from
binutils-dev gets picked up.

Basically, libiberty-dev is unusable (worse than unusable -- it causes
build breaks), if libbfd-dev is installed.

>From what I can tell, libiberty-20141014 also suffers from this problem...

-----
You may ask: why am I using libiberty at all? The answer is dumb: I
want to get pretty-printing for stack traces, by including
line-numbers -- this is something the basic glibc backtrace_symbols()
does not currently do.  It would be nice if it did ... :-)

--- End Message ---
--- Begin Message ---
Version: 20161017-1

At least in current unstable, the ansi.h file matches.

--- End Message ---

Reply to: