Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 20 Dec 2019 10:22:58 +0000
From:      bugzilla-noreply@freebsd.org
To:        ports-bugs@FreeBSD.org
Subject:   [Bug 242672] science/py-scikit-learn: Fails due to unresolved symbols (py36-scikit-learn-0.20.3_1)
Message-ID:  <bug-242672-7788-PN5MdVc7zP@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-242672-7788@https.bugs.freebsd.org/bugzilla/>
References:  <bug-242672-7788@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=3D242672

--- Comment #7 from Andy Mender <andymenderunix@gmail.com> ---
(In reply to Kubilay Kocak from comment #6)

> That's good, we can set this issue to depend on bug 238718 as the update =
includes something that presumably resolves the bug, unless this is incorre=
ct (please let us know).

I think it makes sense to make my bug report depend on bug 238718. Since I
tested py-scikit-learn version 0.20 in both Python2.7 and Python3.6, and saw
the error there, it seems the update to 0.22 fixed the issue.

> Yes please, because conversely, if the update doesn't (actually, either w=
ay), this will highlight LDFLAGS=3D-lblas removal in previous revisions are=
 a contributor, if not cause of the issue.

I got a little lost here. Should I then try version 0.20 with the explicit
`LDFLAGS=3D-lblas` flag? Because if version 0.22 solved the problem, direct=
ly
linking against `cblas` that way won't change anything or will it?

I'm clear on the rest of the items you listed :).

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-242672-7788-PN5MdVc7zP>