Bug 2161618

Hello,

Please note that this comment was generated automatically by https://pagure.io/releng/blob/main/f/scripts/ftbfs-fti/follow-policy.py
If you feel that this output has mistakes, please open an issue at https://pagure.io/releng/

This is the first reminder (step 3 from https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/#_package_removal_for_long_standing_ftbfs_and_fti_bugs).

If you know about this problem and are planning on fixing it, please acknowledge so by setting the bug status to ASSIGNED. If you don't have time to maintain this package, consider orphaning it, so maintainers of dependent packages realize the problem.

I am going to look into it, unless you are faster, Thomas :-) I have a bigger update in progress, but need to finish it before doing an official build.

This bug appears to have been reported against 'rawhide' during the Fedora Linux 38 development cycle.
Changing version to 38.

Hi.

This bug has found it's way into Fedora 38 release. Will GHDL be removed from Fedora soon, or will someone fix this issue?

A workaround while waiting for the fix is to install libgnat from F37 via rpm before using dnf to install ghdl.

It also fails to build under mock mock -r /etc/mock/fedora-38-x86_64.cfg ghdl-0.38~dev-17.20201208git83dfd49.fc38.src.rpm --rebuild

RPM build warnings:

RPM build errors:
error: Bad exit status from /var/tmp/rpm-tmp.jnudbe (%build)
    %patchN is deprecated (19 usages found), use %patch N (or %patch -P N)
    Bad exit status from /var/tmp/rpm-tmp.jnudbe (%build)
Finish: rpmbuild ghdl-0.38~dev-17.20201208git83dfd49.fc38.src.rpm
Finish: build phase for ghdl-0.38~dev-17.20201208git83dfd49.fc38.src.rpm
ERROR: Exception(ghdl-0.38~dev-17.20201208git83dfd49.fc38.src.rpm) Config(fedora-38-x86_64) 1 minutes 1 seconds
INFO: Results and/or logs in: /var/lib/mock/fedora-38-x86_64/result
ERROR: Command failed: 
 # /usr/bin/systemd-nspawn -q -M 5005cbdf71b246da8aec7c73646f751a -D /var/lib/mock/fedora-38-x86_64/root -a -u mockbuild --capability=cap_ipc_lock --bind=/tmp/mock-resolv.k84po4cu:/etc/resolv.conf --bind=/dev/btrfs-control --bind=/dev/mapper/control --bind=/dev/loop-control --bind=/dev/loop0 --bind=/dev/loop1 --bind=/dev/loop2 --bind=/dev/loop3 --bind=/dev/loop4 --bind=/dev/loop5 --bind=/dev/loop6 --bind=/dev/loop7 --bind=/dev/loop8 --bind=/dev/loop9 --bind=/dev/loop10 --bind=/dev/loop11 --console=pipe --setenv=TERM=vt100 --setenv=SHELL=/bin/bash --setenv=HOME=/builddir --setenv=HOSTNAME=mock --setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin --setenv=PROMPT_COMMAND=printf "\033]0;<mock-chroot>\007" --setenv=PS1=<mock-chroot> \s-\v\$  --setenv=LANG=C.UTF-8 --resolv-conf=off bash --login -c /usr/bin/rpmbuild -bb --noclean --target x86_64 --nodeps /builddir/build/SPECS/ghdl.spec

+ ./configure --prefix=/usr --disable-werror --with-llvm-config=/usr/bin/llvm-config --enable-libghdl --enable-synth
Use full IEEE library
Build machine is: x86_64-redhat-linux
Unhandled version llvm 17.0.2
error: Bad exit status from /var/tmp/rpm-tmp.DGCIMX (%build)

RPM build warnings:

RPM build errors:
    %patchN is deprecated (19 usages found), use %patch N (or %patch -P N)
    Bad exit status from /var/tmp/rpm-tmp.DGCIMX (%build)
Finish: rpmbuild ghdl-0.38~dev-18.20201208git83dfd49.fc39.src.rpm
Finish: build phase for ghdl-0.38~dev-18.20201208git83dfd49.fc39.src.rpm
ERROR: Exception(ghdl-0.38~dev-18.20201208git83dfd49.fc39.src.rpm) Config(fedora-39-x86_64) 1 minutes 55 seconds
INFO: Results and/or logs in: /var/lib/mock/fedora-39-x86_64/result
ERROR: Command failed: 
 # /usr/bin/systemd-nspawn -q -M 9e317704f7be41b9a26ccd41b7b8946e -D /var/lib/mock/fedora-39-x86_64/root -a -u mockbuild --capability=cap_ipc_lock --bind=/tmp/mock-resolv.ph1gwcd0:/etc/resolv.conf --bind=/dev/btrfs-control --bind=/dev/mapper/control --bind=/dev/fuse --bind=/dev/loop-control --bind=/dev/loop0 --bind=/dev/loop1 --bind=/dev/loop2 --bind=/dev/loop3 --bind=/dev/loop4 --bind=/dev/loop5 --bind=/dev/loop6 --bind=/dev/loop7 --bind=/dev/loop8 --bind=/dev/loop9 --bind=/dev/loop10 --bind=/dev/loop11 --console=pipe --setenv=TERM=vt100 --setenv=SHELL=/bin/bash --setenv=HOME=/builddir --setenv=HOSTNAME=mock --setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin '--setenv=PROMPT_COMMAND=printf "\033]0;<mock-chroot>\007"' '--setenv=PS1=<mock-chroot> \s-\v\$ ' --setenv=LANG=C.UTF-8 --resolv-conf=off bash --login -c '/usr/bin/rpmbuild -bb --noclean --target x86_64 --nodeps /builddir/build/SPECS/ghdl.spec'

and

Any news ? Is their a way I can help ?

Unfortunately I have no time to work on ghdl currently. It would be useful to have a PR to rebase ghdl to v3.0 and recent gcc, likely with backported patches for new LLVM or such.

Seems I have found my previous work where I rebased ghdl to 2.0.0 and gcc to 12. But I recall having some issues with the directory layout in the newer ghdl releases ...

Build of version 3.0.0 is in progress and should succeed based on my scratch build. Please report any issues in new bug(s), ideally as PRs fixing them.

Also, we should be able to submit builds for F-39 and F-38 with zero or minimal changes.

FEDORA-2024-1187d830e4 (ghdl-3.0.0-1.20230308git7de967c.fc40) has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-1187d830e4

FEDORA-2024-1187d830e4 (ghdl-3.0.0-1.20230308git7de967c.fc40) has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.

FEDORA-2024-e9dec9cec8 (ghdl-3.0.0-1.20230308git7de967c.fc39) has been submitted as an update to Fedora 39.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-e9dec9cec8

FEDORA-2024-68182e2780 (ghdl-3.0.0-1.20230308git7de967c.fc38) has been submitted as an update to Fedora 38.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-68182e2780

FEDORA-2024-e9dec9cec8 has been pushed to the Fedora 39 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-e9dec9cec8`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-e9dec9cec8

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

FEDORA-2024-68182e2780 has been pushed to the Fedora 38 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-68182e2780`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-68182e2780

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

On Fedora 39 (Workstation Edition), I tried to install ghdl-3.0.0-1 from the repo updates-testing with this command:

```
sudo dnf install --enablerepo=updates-testing --refresh ghdl
```

But I got a missing dependencies error:

```
- nothing provides libgnat-12.so()(64bit) needed by ghdl-0.38~dev-16.20201208git83dfd49.fc37.x86_64 from fedora
- nothing provides libgcc >= 14.0.1 needed by ghdl-3.0.0-1.20230308git7de967c.fc39.x86_64 from updates-testing
```

grr, you are right, I have rebased the f38/f39 branches too far ... 

But nothing that couldn't be fixed, stay tuned.

FEDORA-2024-e9dec9cec8 has been pushed to the Fedora 39 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-e9dec9cec8`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-e9dec9cec8

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

FEDORA-2024-68182e2780 has been pushed to the Fedora 38 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-68182e2780`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-68182e2780

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

The installation worked for me, from the `updates-testing` repo.

(I cannot report a feedback on bodhi, I have issue to login.)