Package Details: ghdl-llvm-git 2.0.0dev.r6945.gaee3585af-4

Git Clone URL: (read-only, click to copy)
Package Base: ghdl-llvm-git
Description: VHDL simulator - LLVM back-end
Upstream URL:
Licenses: GPL2
Conflicts: ghdl, ghdl-gcc-git, ghdl-mcode-git
Provides: ghdl, ghdl-git
Submitter: marzoul
Maintainer: marzoul (xiretza)
Last Packager: xiretza
Votes: 3
Popularity: 0.000000
First Submitted: 2015-12-02 23:00 (UTC)
Last Updated: 2022-01-17 16:19 (UTC)

Required by (8)

Sources (1)

Latest Comments

xiretza commented on 2021-05-14 18:34 (UTC) (edited on 2021-05-14 18:34 (UTC) by xiretza)

Could you add the following before ./configure (as outlined in the wiki)? The recent upstream makefile changes broke debug builds because LLVM can't handle -fvar-tracking-assignments from DEBUG_C(XX)FLAGS.


marzoul commented on 2021-05-09 14:35 (UTC)

Thanks for reporting. I have updated the PKGBUILD with unconditional removal of ghwdump for now.

xiretza commented on 2021-05-09 11:00 (UTC)

Alright, the situation is the following: the GHW libraries and tooling are developed as part of ghdl and the sources are periodically synced over to gtkwave to maintain compatibility. gtkwave has always built and installed ghwdump, while ghdl only started doing this recently. Thus, for the latest releases available in the repos, gtkwave provides ghwdump and ghdl doesn't. As soon as ghdl cuts another release, this same conflict will arrive in the repos though, and we'll have to see how maintainers handle it then.

For now, maintaining parity with the repos and deleting ghwdump in ghdl-*-git is probably the best option.

Sven commented on 2021-05-09 10:44 (UTC)

@xiretza I asked the maintainer of gtkwave-gtk3 here on AUR. He suggested that ghwdump be removed from ghdl. Could you guys try to reach some agreement so that I can use ghdl2 and gtkwave together?

xiretza commented on 2021-05-09 10:40 (UTC)

That should be fixed in gtkwave, the upstream for GHW is ghdl.

Sven commented on 2021-05-09 10:38 (UTC)

As far as I understand, ghdl is oftem used together with gtkwave. But this package has a file collision with gtkwave. I tried both community/gtkwave and aur/gtkwave-gtk3. Both of them contain /usr/bin/ghwdump.

xiretza commented on 2021-04-26 20:11 (UTC)

Sounds good, though most distros on other architectures probably use --ignorearch anyway (since only very few AUR packages are marked as working on non-x86_64)

marzoul commented on 2021-04-26 20:06 (UTC)

It seems that we could use the following list of architectures, what do you think ? arch=('x86_64' 'i686' 'pentium4' 'arm' 'armv6h' 'armv7h' 'aarch64')

marzoul commented on 2021-04-26 19:57 (UTC)

You're right. Too bad that there is no official convention for packages that can be built on any architecture even if the resulting package file is architecture-dependent. Now I've realized this, I have a feeling that this is missing in makepkg xD

xiretza commented on 2021-04-26 11:39 (UTC)

This package should definitely not be arch=('any') (same for ghdl-gcc-git), and the license name should be GPL2 for all three packages (since that's what's in /usr/share/licenses/common/).

csantosb commented on 2020-02-21 21:19 (UTC)

@marzoul Just for the record, it compiles without any issue and performs great now with llvm 9.

marzoul commented on 2019-04-03 20:44 (UTC)

@csantosb : Thank you for reporting, indeed version 8 is not officially handled by GHDL configure script. I updated PKGBUILD with the version check. Note that they don't often check with newer llvm/clang versions, maybe it does work when the check is bypassed in the configure script, if needed...

csantosb commented on 2019-04-01 20:45 (UTC)

Using latest llvm8 I get

Unhandled version llvm 8.0.0

Is that expected ? I had to build using llvm7, updating pkgbuild accordingly.

marzoul commented on 2016-12-18 00:33 (UTC)

Thanks for reporting. I'll investigate as soon as possible.

melko commented on 2016-12-17 13:03 (UTC)

Seems std_standard.o isn't copied into DESTDIR when building with more than one thread. Unsetting MAKEFLAGS in the build function fixed the issue for me.