Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

library 29IEEE not found #385

Closed
xXplutoXx opened this issue Aug 15, 2019 · 3 comments
Closed

library 29IEEE not found #385

xXplutoXx opened this issue Aug 15, 2019 · 3 comments

Comments

@xXplutoXx
Copy link

xXplutoXx commented Aug 15, 2019

Since updating to nvc 1.5 on Mac OS, I have a strange issue for designs using std_logic_arith (it appeared for larger designs an I was not able so far to isolate a small design where this happens):

During simulation, I get like this:

	Process :testbench_fpmult_8_26_8_26_8_26_uid2_f400_uid3_f400_uid69:test:line_1210
	File ../lib/synopsys/std_logic_arith.vhd, Line 255
** Error: library 29IEEE not found in:
            /Users/<my home>/.nvc/lib
            /usr/local/share/nvc

It looks to me like a kind or parser error as when I create a folder named "29IEEE" and put the "IEEE" content inside, everything works as expected (this is my current workaround to continue the work).
Any idea?

@nickg
Copy link
Owner

nickg commented Aug 15, 2019

Are you able to build from the master branch and see if the error still occurs? Also it would be useful if you could a stack trace when that "library 29IEEE not found in" error is reported. It comes from lib_find in lib.c (line 455 in master). If you could put a breakpoint there in gdb and send the stack trace that would be great.

@nickg
Copy link
Owner

nickg commented Apr 3, 2021

Closing this due to lack of activity. The library loading code has changed somewhat since 2019 so it might be fixed already. If not please reopen and try to get a stack trace from gdb as described above.

@nickg nickg closed this as completed Apr 3, 2021
@nickg
Copy link
Owner

nickg commented Apr 9, 2021

I think I found the cause of this. It should be fixed in 1.5.1 release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants