Package Details: yosys-git 0.9+3627.r10276.e919d0c1-1

Git Clone URL: (read-only, click to copy)
Package Base: yosys-git
Description: A framework for RTL synthesis
Upstream URL:
Keywords: fpga
Licenses: custom:ISC
Conflicts: yosys
Provides: yosys=0.9+3627.r10276.e919d0c1
Submitter: sebo
Maintainer: thasti
Last Packager: thasti
Votes: 13
Popularity: 0.000028
First Submitted: 2015-10-05 19:00
Last Updated: 2020-10-20 17:42

Required by (8)

Sources (2)

Latest Comments

« First ‹ Previous 1 2 3 4 5 Next › Last »

potatoe commented on 2019-11-17 23:01

I think the linking problems are maybe due to a change in python-config (a script in /usr/bin included with python) in 3.8, specifically: which dropped the -lpython3.8 from the output of python-config --ldflags. The new way seems to be to call python-config with an extra flag --embed to include the python library in addition to the regular --ldflags, per .

So I guess that might mean it's an upstream issue, yosys's Makefile's usage of python-config (or $(PYTHON_EXECUTABLE)-config, rather) could be updated to be compatible with python 3.8? It will need a few extra fallbacks around trying calls with and without --embed to continue working on both 3.8 and older ones (which don't support passing an --embed flag), though.

thasti commented on 2019-11-17 12:11

Is it expected that building against boost_python3 now requires this additional linker flag? I wonder whether this is to be considered a bug in the yosys Makefile (in which case I would file an issue with yosys upstream) or an unintended change in the behavior of boost-libs after updating to Python3.8.

vogelchr commented on 2019-11-17 12:01

Adding this to the PKGBUILD's build() allows makepkg to build yosys successfully.

echo "BOOST_PYTHON_LIB=-lboost_python38 -lpython3.8" >>Makefile.conf

Not adding the -lpython3.8 for me results in a huge amount of unresolved symbols, and I cannot see -lpython being added to the build command when manually running "make PRETTY=0".

thasti commented on 2019-11-16 18:45

@gnurise: It looks like it. It appears as if the yosys Makefile tries to do it's check for which libboost to use, but runs into the same compilation errors you get when providing the correct library manually. Not quite sure where to flag this, but boost-libs could be the best fit I believe.

It appears to me that building any C program with -lboost_python is broken as it stands now.

gururise commented on 2019-11-16 18:33

@thasti wonder if this has something to do with the recent upgrade in Arch to Python 3.8? I tried:

export BOOST_PYTHON_LIB=/lib/

But ended up with a bunch of compilation errors complaining about symbols not found.

thasti commented on 2019-11-16 09:14

@gnurise: Can't reproduce with current git master. For me, no modifications of the PKGBUILD are required. Are you sure boost is installed and functional on your system?

EDIT: Actually can reproduce after updating other packages. Potentially something in boost library contents changed. Will investigate.

gururise commented on 2019-11-16 08:04

Compile fails:

echo 'CONFIG := gcc' > Makefile.conf

[Makefile.conf] CONFIG := gcc

[Makefile.conf] ENABLE_LIBYOSYS=1

[Makefile.conf] ENABLE_PYOSYS=1

Makefile:323: *** BOOST_PYTHON_LIB could not be detected. Please define manualy. Stop.

novenary commented on 2019-07-05 08:56

@swedishhat: I just checked, yosys does indeed require extra/boost as a makedepend, and extra/boost-libs as a runtime dependency (according to ldd output). The readme on github also mentions the dependency. namcap also complains about it: yosys-git E: Dependency boost-libs detected and not included (libraries ['usr/lib/', 'usr/lib/'] needed in files ['usr/lib/python3.7/site-packages/pyosys/'])

novenary commented on 2019-07-02 18:17

Installing extra/boost allows the build to complete, I haven't checked whether the runtime libs are required and I won't have access to a computer until this weekend. I believe namcap can detect missing dependencies on shared libraries if you'd like to check that yourself.

swedishhat commented on 2019-07-02 18:09

@streetwalrus: did you resolve this? If not, try installing extra/boost-libs to see if that resolves the dependency problem.