Bug 225621

Summary: devel/llvm50: llvm-config --system-libs says "-l/usr/lib/libexecinfo.so"
Product: Ports & Packages Reporter: Thomas Munro <munro>
Component: Individual Port(s)Assignee: Brooks Davis <brooks>
Status: Closed FIXED    
Severity: Affects Only Me CC: preetpal.sohal, swills
Priority: --- Flags: bugzilla: maintainer-feedback? (brooks)
Version: Latest   
Hardware: Any   
OS: Any   

Description Thomas Munro 2018-02-02 02:11:11 UTC 
$ /usr/local/llvm50/bin/llvm-config --system-libs
-lrt -l/usr/lib/libexecinfo.so -ltinfo -lpthread -lz -lm

$ cc $(/usr/local/llvm50/bin/llvm-config --system-libs) test.c
/usr/bin/ld: cannot find -l/usr/lib/libexecinfo.so
cc: error: linker command failed with exit code 1 (use -v to see invocation)

Shouldn't that say -lexecinfo instead of -l/usr/lib/libexecinfo.so?
Comment 1 Thomas Munro 2018-02-02 03:23:04 UTC 
I should probably add that I installed llvm50 via pkg.
Comment 2 Brooks Davis freebsd_committer freebsd_triage 2018-02-02 17:27:46 UTC 
This has been fixed in current.  If it's a major issue and you can't switch your pkg repo to current I can look at merging the fix to the quarterly branch.  Closing for now, but do reply if you need it fixed in the quarterly branch.
Comment 3 Brooks Davis freebsd_committer freebsd_triage 2018-02-02 17:32:36 UTC 
I now see that this change was merged last night.
Comment 4 Preetpal Sohal 2018-02-05 19:49:07 UTC 
I believe that this fix not being in quarterly results in other packages such as flang not becoming available in the quarterly branch.

See: https://forums.freebsd.org/threads/64517/
Comment 5 Brooks Davis freebsd_committer freebsd_triage 2018-02-05 20:22:02 UTC 
This was fixed in 2018Q1 with https://svnweb.freebsd.org/ports?view=revision&revision=460693
Comment 6 Brooks Davis freebsd_committer freebsd_triage 2018-02-05 20:24:31 UTC 
Correction, I see the report is that that the merge broke flang, not that the fix was missing.  That should have been reported clearly in a separate bug.
Comment 7 Preetpal Sohal 2018-02-06 23:25:22 UTC 
Apologies for the mistaken assessment. If the merge of the fix broke flang (and possibly other packages?), should a bug report be made for the flang port or is the problem with this port (since the merged change broke packages that rely on it)?
Comment 8 Brooks Davis freebsd_committer freebsd_triage 2018-02-07 00:00:47 UTC 
It looks like r459134 needs to be merged to 2018Q1 to fix clang-clang.
Comment 9 Preetpal Sohal 2018-02-07 04:09:45 UTC 
I have made a request for that revision of flang to be merged into the 2018Q1 branch (in an associated bug that was closed as a result of that revision).

See: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225174#c7