Bug 219019 - print/texlive-base: Fails to configure if LOCALBASE != /usr/local
Summary: print/texlive-base: Fails to configure if LOCALBASE != /usr/local
Status: In Progress
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: Kubilay Kocak
Keywords: needs-qa
Depends on:
Reported: 2017-05-02 19:36 UTC by John Hein
Modified: 2019-06-01 06:39 UTC (History)
2 users (show)

See Also:
bugzilla: maintainer-feedback? (hrs)
koobs: merge-quarterly?

[patch] support non-default LOCALBASE (1.07 KB, patch)
2017-05-02 19:36 UTC, John Hein
jcfyecrayz: maintainer-approval? (hrs)
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description John Hein 2017-05-02 19:36:27 UTC
Created attachment 182251 [details]
[patch] support non-default LOCALBASE

If LOCALBASE is defined to be something other than /usr/local, texlive-base fails at configure time:

checking whether the c++ linker (/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... freebsd10.3 ld.so
checking how to hardcode library paths into programs... immediate
checking whether ln -s works... yes
configure: You requested to build `web2c' using an installed `kpathsea' version,
configure:     which requires to locate the <kpathsea/paths.h> header file.
configure: error: Sorry, not found under any of: /usr/include /usr/local/include *****
===>  Script "configure" failed unexpectedly.
Comment 1 John Hein 2017-09-07 14:21:07 UTC
Maintainer timeout?
Comment 2 Zsolt Udvari 2017-10-03 14:02:12 UTC
I created an update-to-2017 patch (see #211997). I think would be better to update to 2017 and check this bug. But no reaction for two months :(
Could you add #211997 to "Depends on" please?
Comment 3 John Hein 2018-04-18 03:55:51 UTC
Fixing this problem does not depend on updating.  The fix here can be applied independently (i.e., before any update while waiting for it to land, or after - likely with a refresh to the patch).  But I noted the update in 'See Also'.