Bug 249328 - editors/libreoffice: link failure on canvasdemo
Summary: editors/libreoffice: link failure on canvasdemo
Status: Open
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-office (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-09-15 08:48 UTC by Bertrand Petit
Modified: 2020-10-21 11:02 UTC (History)
3 users (show)

See Also:
bugzilla: maintainer-feedback? (office)


Attachments
Ports configuration tree of the affected host (A) (50.89 KB, text/plain)
2020-09-15 20:21 UTC, Bertrand Petit
no flags Details
Ports configuration tree of the unaffected host (B) (45.58 KB, text/plain)
2020-09-15 20:21 UTC, Bertrand Petit
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Bertrand Petit 2020-09-15 08:48:31 UTC
The libreoffice port revision 7.0.1.2 fails to link canvasdemo

[...]
[build LNK] Executable/canvasdemo
S=/usr/obj/ports/usr/ports/editors/libreoffice/work/libreoffice-7.0.1.2 && I=$S/instdir && W=$S/workdir &&  c++ -pthread    -Wl,-z,origin '-Wl,-rpath,$ORIGIN/../Library' -Wl,-rpath-link,$I/program -fstack-protector-strong -Wl,-rpath-link,/lib:/usr/lib -Wl,-z,combreloc  -Wl,--hash-style=gnu  -Wl,-Bsymbolic-functions -L$W/LinkTarget/StaticLibrary -L$I/sdk/lib  -L$I/program  -L$I/program  -L$W/LinkTarget/Library -L/usr/local/lib -Wl,-rpath,/usr/local/lib -fstack-protector-strong    -L/usr/local/lib  $W/CxxObject/canvas/workben/canvasdemo.o      -Wl,--start-group $W/LinkTarget/StaticLibrary/libvclmain.a $W/LinkTarget/StaticLibrary/libglxtest.a -lm  -lX11   -Wl,--end-group -Wl,--no-as-needed -lbasegfxlo -lcomphelper -luno_cppu -luno_cppuhelpergcc3 -ltllo -luno_sal -luno_salhelpergcc3 -lvcllo  -o $W/LinkTarget/Executable/canvasdemo 
/usr/obj/ports/usr/ports/editors/libreoffice/work/libreoffice-7.0.1.2/instdir/program/libskialo.so: undefined reference to `XGetXCBConnection'
c++: error: linker command failed with exit code 1 (use -v to see invocation)
[...]

Shouldn't -lX11-xcb be used instead of -lX11?
Comment 1 Li-Wen Hsu freebsd_committer 2020-09-15 15:08:44 UTC
Just wanted to make sure, do you use the default options or there are some customized settings?
Comment 2 Bertrand Petit 2020-09-15 20:21:03 UTC
Created attachment 217980 [details]
Ports configuration tree of the affected host (A)
Comment 3 Bertrand Petit 2020-09-15 20:21:37 UTC
Created attachment 217981 [details]
Ports configuration tree of the unaffected host (B)
Comment 4 Bertrand Petit 2020-09-15 20:27:48 UTC
I attempted two installations of lo on two different hosts with two different outcomes: one for which the failure is reported above (host A); one on which the port was successfully installed (host B). For both hosts I attached the full ports configuration tree.

Host A runs 11-STABLE (rev 365447), host B runs 12-STABLE (rev 360207).