Bug#616362: gcc-snapshot: link failure with gnat (/usr/bin/ld: cannot find -laddr2line)
Євгеній Мещеряков writes:
> Hello,
>
> I reported that bug because I tried to compile spark-gpl.
I'm interested in that; I'm sure others are, too. Could you please
announce your effort on debian-...@lists.debian.org? It must be
possible to join efforts. IIUC, the main stumbling block is, or was,
that some SPARK tools are written in Prolog and require a non-free
Prolog compiler. Do you know anything about that?
> Compilation failed with stack overflow or invalid memory access. It
> was compiled fine with gcc-snapshot, but linking failed. So I guess
> the bug with stack overflow was fixed somewhere between gcc-4.4 and
> 4.6. Or maybe it was introduced by patches...
This bug has quite a complex history. Upstream (AdaCore) supports
symbolic tracebacks through a library called libaddr2line.a, which they
produce from their own patched binutils sources. This has been so for
as long as I can remember. I patched gnat 3.15p back in 2005 to support
symbolic tracebacks without requiring this special library (doing a
fork()/exec() of addr2line instead). This patch was broken by an
upstream change in gnat-4.3 and re-fixed in gnat-4.4 (=4.4.4-4).
> 3 березня 2011 о 21:07 +0100 Ludovic Brenta написав(-ла):
>> This is because the patch ada-symbolic-tracebacks.diff has not been
>> ported to gcc-snapshot.
> I see that this patch is present in gcc-snapshot source, and it is
> even applied (at least at the beginning of the build, I do not have
> enough free time now to build it all). But installed g-trasym.adb
> really contains pragma Linker_Options ("-laddr2line");. Is it intended
> behaviour or there is something wrong here?
Yes, this is wrong. Debian has no such library as libaddr2line, so the
Linker_Options should not be there. The patch
ada-symbolic-tracebacks.diff normally removes it but, as I said, it has
not yet been ported to gcc-snapshot, so it leaves the sources in an
inconsistent state.
> BTW do you think it is worth it to submit bug reports to the gnat
> bugzilla? I see there are many reports from years ago with no
> comment. Is it used at all by upstream?
Submitting bugs in the bugzilla is always a good idea. AdaCore look at
these bugs occasionally but not systematically; they have already fixed
a majority of them (see the closed PRs). (It is only natural that they
give priority to bugs submitted by paying customers). In addition,
contributors outside AdaCore occasionally step in.
Thanks for your interest.
--
Ludovic Brenta.
--
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87lj0swmr8@ludovic-brenta.org
Bug#616362: gcc-snapshot: link failure with gnat (/usr/bin/ld: cannot find -laddr2line)
Hello,
I reported that bug because I tried to compile spark-gpl. Compilation
failed with stack overflow or invalid memory access. It was compiled
fine with gcc-snapshot, but linking failed. So I guess the bug with
stack overflow was fixed somewhere between gcc-4.4 and 4.6. Or maybe it
was introduced by patches...
3 березня 2011 о 21:07 +0100 Ludovic Brenta написав(-ла):
> This is because the patch ada-symbolic-tracebacks.diff has not been
> ported to gcc-snapshot.
I see that this patch is present in gcc-snapshot source, and it is even
applied (at least at the beginning of the build, I do not have enough
free time now to build it all). But installed g-trasym.adb really
contains pragma Linker_Options ("-laddr2line");. Is it intended
behaviour or there is something wrong here?
> I do not work with, or support, gcc-snapshot. My policy is to
> concentrate on, and support, only one version of gnat at a time;
> currently this is gnat-4.4, so you can expect this bug never to be fixed
> in gcc-snapshot. Instead, you can expect a future gnat-4.5 or gnat-4.6
> with proper support for symbolic tracebacks. If you would like to help,
> please contact me.
I just started to learn Ada, so I do not think there are many thing I
can help with.
BTW do you think it is worth it to submit bug reports to the gnat bugzilla?
I see there are many reports from years ago with no comment. Is it used
at all by upstream?
Regards,
Eugeniy Meshcheryakov
signature.asc
Description: Digital signature
Processed: Re: Bug#616362: gcc-snapshot: link failure with gnat (/usr/bin/ld: cannot find -laddr2line)
Processing commands for cont...@bugs.debian.org: > tags 616362 wontfix Bug #616362 [gcc-snapshot] gcc-snapshot: link failure with gnat (/usr/bin/ld: cannot find -laddr2line) Added tag(s) wontfix. > thanks Stopping processing here. Please contact me if you need assistance. -- 616362: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=616362 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.129918284329465.transcr...@bugs.debian.org
Bug#616362: gcc-snapshot: link failure with gnat (/usr/bin/ld: cannot find -laddr2line)
tags 616362 wontfix thanks This is because the patch ada-symbolic-tracebacks.diff has not been ported to gcc-snapshot. I do not work with, or support, gcc-snapshot. My policy is to concentrate on, and support, only one version of gnat at a time; currently this is gnat-4.4, so you can expect this bug never to be fixed in gcc-snapshot. Instead, you can expect a future gnat-4.5 or gnat-4.6 with proper support for symbolic tracebacks. If you would like to help, please contact me. -- Ludovic Brenta (Debian gnat maintainer). -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87ei6ot1ce@ludovic-brenta.org
Bug#616362: gcc-snapshot: link failure with gnat (/usr/bin/ld: cannot find -laddr2line)
Package: gcc-snapshot Version: 20110226-1 Severity: normal Linking of Ada program fails if it depends on GNAT.Traceback.Symbolic: % cat testcase.adb with GNAT.Traceback.Symbolic; procedure TestCase is begin null; end TestCase; % gnatmake testcase.adb gcc -c testcase.adb gnatbind -x testcase.ali gnatlink testcase.ali /usr/bin/ld: cannot find -laddr2line collect2: ld returned 1 exit status gnatlink: error when calling /usr/lib/gcc-snapshot/bin/gcc gnatmake: *** link failed. This is the same bug as http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=322849 . It was fixed in gcc-4.1. This bug is not present in gnat-4.4. I'm using PATH and LD_LIBRARY_PATH settings as described in README.Debian. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38-rc6+ (SMP w/2 CPU cores; PREEMPT) Locale: LANG=uk_UA.UTF-8, LC_CTYPE=uk_UA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gcc-snapshot depends on: ii binutils 2.21.0.20110302-1 The GNU assembler, linker and bina ii ecj-gcj [libecj-java-g 3.5.1-1 standalone version of the Eclipse ii libc6 2.11.2-13 Embedded GNU C Library: Shared lib ii libc6-dev 2.11.2-13 Embedded GNU C Library: Developmen ii libc6-dev-i386 2.11.2-13 Embedded GNU C Library: 32-bit dev ii libc6-i386 2.11.2-13 Embedded GNU C Library: 32-bit sha ii libecj-java-gcj3.5.1-1 Eclipse Java compiler (native libr ii libgmp3c2 2:4.3.2+dfsg-1Multiprecision arithmetic library ii libmpc20.9-1 multiple precision complex floatin ii libmpfr4 3.0.0-7 multiple precision floating-point ii python 2.6.6-3+squeeze5 interactive high-level object-orie ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime gcc-snapshot recommends no packages. Versions of packages gcc-snapshot suggests: pn binutils-gold (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110303191310.10313.47146.report...@openfonts.org
