Bug#759407: gnat-4.9: gnat1 not found on kfreebsd-i386
reassign 759407 src:gcc-4.9
thanks
Hello,
Svante is correct on one point: some version of gcc-4.9 broke gnat-4.9
on kfreebsd-i386 at least. Proof: on August 11, gnat-4.9 (=4.9.1-1)
worked perfectly well when combined with gcc-4.9 (exact version
unspecified):
https://buildd.debian.org/status/fetch.php?pkg=libtemplates-parser&arch=kfreebsd-i386&ver=11.8.2014-3&stamp=1407787293
The symptoms appeared later, still with gnat-4.9 (=4.9.1-1) but with
a later gcc-4.9; not a snapshot. On August 24:
https://buildd.debian.org/status/fetch.php?pkg=gnat-gps&arch=kfreebsd-i386&ver=5.3-3&stamp=1408919003
Between these two dates (August 11 and August 24), there were no
uploads
of gnat-4.9 but there were some uploads of gcc-4.9, therefore gcc-4.9
must have broken something, possibly in the target triplet or directory
where it looks for gnat1.
Possibly, this bug has already been fixed by the last change in this
upload:
gcc-4.9 (4.9.1-11) unstable; urgency=medium
* Update to SVN 20140830 (r214759) from the gcc-4_9-branch.
* Update cross installation patches for the branch.
* Use the base version (4.9) when accessing files in gcc_lib_dir.
-- Matthias Klose <doko@debian.org> Sat, 30 Aug 2014 22:05:47 +0200
I'll try to check this (on kfreebsd-i386) over the weekend.
This particular bug is for kfreebsd-i386 only. hurd-i386 has similar
symptoms on different dates (for example, the build of gnat-gps
(=5.3-3)
succeeded on hurd-i386 when it failed on kfreebsd-i386). I propose to
use #761248 (severity important) to track the issue on hurd-i386, if
it is different.
--
Ludovic Brenta.
Reply to: