Bug 203968 - graphics/graphviz fails to register plugins
Summary: graphics/graphviz fails to register plugins
Status: Closed DUPLICATE of bug 203537
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Many People
Assignee: Dirk Meyer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-10-22 23:26 UTC by leventelist
Modified: 2015-10-29 06:21 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description leventelist 2015-10-22 23:26:31 UTC 
Installing of the port OR the package gives this:

Unable to find pthread_create symbol. Aborting.
Abort trap (core dumped)

The exe is installed, however ALL the output drivers are unusable.

It outputs this for ANY -Txx :

There is no layout engine support for "dot"
Perhaps "dot -c" needs to be run (with installer's privileges) to register the plugins?

Perhaps it has to something about this issue:

https://lists.freebsd.org/pipermail/freebsd-ports/2013-February/081302.html
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2015-10-23 00:21:21 UTC 
Fix Summary and assign.
Comment 2 Dirk Meyer freebsd_committer freebsd_triage 2015-10-28 08:02:12 UTC 
Please try a build with option NVTHREADS .

Please report if you have nvidia driver or nor.
Comment 3 leventelist 2015-10-28 19:47:28 UTC 
I can confirm rebuilding with NVTHREADS it works.
Yes, I have an NVIDIA driver.

I'm just wondering why this is connected to the graphic chipset. What if I had AMD GPU?

Lev
Comment 4 Dirk Meyer freebsd_committer freebsd_triage 2015-10-29 06:21:32 UTC 
The nvidia drives changes some libs of the X11 system.
The nvidia libs are build with threads,
The standard libs are build without.

Graphviz does not uses threads,
but when linking with the threaded libs it fails.

This might cause problem for non-threaded applications linking with Graphviz.

*** This bug has been marked as a duplicate of bug 203537 ***