Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 13 Jan 2016 11:55:37 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-ports-bugs@FreeBSD.org
Subject:   [Bug 206194] lang/python27 install fails if misc/compat6x is installed [due to libreadline check]
Message-ID:  <bug-206194-13-MAkKhwQZg6@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-206194-13@https.bugs.freebsd.org/bugzilla/>
References:  <bug-206194-13@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D206194

--- Comment #1 from Kubilay Kocak <koobs@FreeBSD.org> ---
This is interesting. I'll pose some questions (somewhat rhetorically) to he=
lp
us determine if, how and where this issue might be best addressed.

* If compatNx is installed, does that mean the user *always* wants or expec=
ts
*everything* thing to link against compat libraries? There is a user answer=
 to
this question and potentially a ports framework answer, which may be differ=
ent.

* Given the current description of the problem, I would expect *many* ports=
 to
be incorrectly linking against or not finding the expected compat libraries=
, in
this case libreadline via USES. Do we know of any other cases that: a) Fail=
 in
a similar way (not found, whether they fail to package or not), b) Fail in
other ways (linking to different library than expected)

* How will readline.mk decide when to depend on compatNx libraries, rather =
than
either existing base ones, or ones from ports, and on what basis and level =
of
granularity.


* Does, and if so how is this addressed for other libraries provided in
compatNx's that have ports framework and individual port implications?

* What is/are the actual 'root' cause(s) here?=20

lang/python27 is implicated only in so far as it doesn't check whether cert=
ain
C extensions compiled or not, before adding them to the plist. This 'could'=
 be
fixed. This is a fairly common type of failure across many ports, whether by
virtue of a compile failure, or an OPTION.

USES=3Dreadline is implicated only in so far as it does not detect the pres=
ence
of compatNx readline library and provide the necessary *FLAGS to find it.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-206194-13-MAkKhwQZg6>