Your message dated Sat, 17 May 2008 15:27:10 -0600
with message-id <[EMAIL PROTECTED]>
and subject line really close
has caused the Debian Bug report #393831,
regarding FTBFS on ia64: fails with ld assertion failure
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.)


-- 
393831: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=393831
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: ghdl
Version: 0.25+gcc4.1.1-1
Severity: serious

ghdl no longer builds on IA64.  The assertion failure in ld should be
fixed (and I reported a bug upstream already), but apparently this is
still a bug in the package.

http://sourceware.org/bugzilla/show_bug.cgi?id=3351#c11 might give
some clue as to where to start looking.  It might be worth trying to
compile the package with gcc-4.1_4.1.1-7 (the compiler used for the
last successful upload), but otherwise it must be a change between
ghdl 0.24 and 0.25.



> Automatic build of ghdl_0.25+gcc4.1.1-1 on coconut0 by sbuild/ia64 0.49
...
> gnatlink 
> /build/tbm/ghdl-0.25+gcc4.1.1/gcc-4.1.1/build/gcc/vhdl/ortho_gcc-main.ali -o 
> ghdl1 ortho-lang.o gcc-version.o ../gcc/toplev.o ../gcc/libbackend.a 
> ../libcpp/libcpp.a ../libiberty/libiberty.a ../libcpp/libcpp.a 
> ../libiberty/libiberty.a
> /usr/bin/ld: BFD 2.17 Debian GNU/Linux assertion fail ../../bfd/elflink.c:6261
> /usr/bin/ld: BFD 2.17 Debian GNU/Linux internal error, aborting at 
> ../../bfd/elflink.c line 6349 in elf_link_check_versioned_symbol
> 
> /usr/bin/ld: Please report this bug.

-- 
Martin Michlmayr
http://www.cyrius.com/


--- End Message ---
--- Begin Message ---
Version: 0.26+svn94+gcc4.1.2~dfsg-2

Apparently marking as "fixed" doesn't close the bug? Trying it this way 
instead...

-- 
Wesley J. Landaker <[EMAIL PROTECTED]> <xmpp:[EMAIL PROTECTED]>
OpenPGP FP: 4135 2A3B 4726 ACC5 9094  0097 F0A9 8A4C 4CD6 E3D2

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---

Reply via email to