Description of problem: With GCC 4.5 came a libgnat-4.5.0-1 package, which broke dependencies of Ada programs and binaries linked to libgnat-4.4.so. When I tried to rebuild PragmARC I hit an internal error in Gnatmake. PragmARC is a dependency of mine_detector. Thus I have two broken packages that I can't fix. Version-Release number of selected component (if applicable): 4.5.0-1.fc14 How reproducible: Every time, in Koji, Mock under x86-64 F13, and a real i686 Rawhide system. Steps to Reproduce: 1. Try to rebuild PragmARC in Rawhide. Actual results: After Gnatmake has executed Gnatbind it prints these messages: Exception name: SYSTEM.ASSERTIONS.ASSERT_FAILURE Message: namet.adb:616 gnatmake: INTERNAL ERROR. Please report. Expected results: a rebuilt package Additional info:
This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle. Changing version to '14'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This is where it fails: Breakpoint 1, system.assertions.raise_assert_failure (msg=...) at s-assert.adb:43 43 procedure Raise_Assert_Failure (Msg : String) is (gdb) bt #0 system.assertions.raise_assert_failure (msg=...) at s-assert.adb:43 #1 0x080c3366 in namet.get_name_string (id=300000000) at /usr/src/debug/gcc-4.5.0-20100716/gcc/ada/namet.adb:616 #2 0x080c0b03 in mlib.utl.lib_directory () at /usr/src/debug/gcc-4.5.0-20100716/gcc/ada/mlib-utl.adb:613 #3 0x080b89cc in mlib.prj.build_library (in_tree=0x85150a0, gnatbind=..., gnatbind_path=..., gcc=..., gcc_path=..., link=true) at /usr/src/debug/gcc-4.5.0-20100716/gcc/ada/mlib-prj.adb:1548 #4 0x080abdcd in make.gnatmake () at /usr/src/debug/gcc-4.5.0-20100716/gcc/ada/make.adb:5744 #5 0x0804a275 in main (argc=17, argv=0xbffff544, envp=0xbffff58c) at b_gnatm.c:476 #6 0x005f6cf6 in __libc_start_main (main=0x804a230 <main>, argc=17, ubp_av=0xbffff544, init=0x8166d70 <__libc_csu_init>, fini=0x8166dd0 <__libc_csu_fini>, rtld_fini=0x5cbc50 <_dl_fini>, stack_end=0xbffff53c) at libc-start.c:226 #7 0x08049b41 in _start () (gdb) frame 2 #2 0x080c0b03 in mlib.utl.lib_directory () at /usr/src/debug/gcc-4.5.0-20100716/gcc/ada/mlib-utl.adb:613 613 Get_Name_String (Osint.Find_File (Name_Enter, Osint.Library)); (gdb) p Name_Buffer(1 .. Name_Len) $1 = "libgnat.a" (gdb) p Integer(Osint.Library) $2 = 1 (gdb) p Osint.Find_File(Name_Enter, 1) $3 = 300000000 (gdb) p Namet.No_File $4 = 300000000 Lib_Directory tries to find the directory that contains libgnat by looking for libgnat.a, but Find_File returns No_File because libgnat.a is missing. Installing libgnat-static works around the problem when building locally.
It looks like a packaging bug for me (not an issue in GCC itself). I hope it's true.
Created attachment 435931 [details] patch to look for libgnat.so if libgnat.a is missing If Gnat is meant to work with only shared libraries installed, then i guess it's a GCC issue. Otherwise it's a packaging bug. I think this patch will make Gnatmake find the directory even when only the shared libraries are present, but I haven't been able to test it because my attempts to rebuild the GCC packages keep failing in various other places.
I have now confirmed that the patch works on my Rawhide system.
If my patch is unacceptable for some reason, can we please let libgnat-devel require libgnat-static until Gnat learns to function without the static libraries?
*** Bug 709436 has been marked as a duplicate of this bug. ***
*** Bug 690610 has been marked as a duplicate of this bug. ***
Thank you for your bug report. We are sorry, but the Fedora Project is no longer releasing bug fixes or any other updates for this version of Fedora. This bug will be set to CLOSED:WONTFIX to reflect this, but please reopen it if the problem persists after upgrading to the latest version of Fedora, which is available from: http://fedoraproject.org/get-fedora -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
still present in 4.6.2-1.fc17.1
(In reply to comment #10) > still present in 4.6.2-1.fc17.1 And, for the record, in 4.7.0-0.5.fc17.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Gnatmake still doesn't work without libgnat-static installed, and there is still no RPM dependency reflecting this.
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle. Changing version to '23'. (As we did not run this process for some time, it could affect also pre-Fedora 23 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle. Changing version to '28'.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.