Bug 229489 - www/py-notebook: Import error with {numpy,matplotlib,scipy,pandas} libgcc_s.so.1
Summary: www/py-notebook: Import error with {numpy,matplotlib,scipy,pandas} libgcc_s.so.1
Status: Closed Overcome By Events
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: Danilo G. Baio
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-07-03 11:49 UTC by David Kalliecharan
Modified: 2020-03-16 22:50 UTC (History)
5 users (show)

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


Attachments
Jupyter Error output for numpy (2.27 KB, text/plain)
2018-07-03 11:49 UTC, David Kalliecharan
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description David Kalliecharan 2018-07-03 11:49:55 UTC
Created attachment 194855 [details]
Jupyter Error output for numpy

Installed py36-notebook from packages will start up fine. However, attempting to import {numpy,matplotlib,scipy,pandas} will cause an Import error about libgcc_s.so.1 not being correct. 

Importing {numpy,matplotlib,scipy,pandas} into ipython3-3.6 terminal, or python3 directly works as expected. 

Attached is the error output from jupyter for numpy specifically.
Comment 1 Kevin Zheng 2018-07-08 22:49:43 UTC
Issue described here:
https://wiki.freebsd.org/libgcc%20problem

My personal workaround is to:
env LD_LIBRARY_PATH=/usr/local/lib/gcc6

Before running anything the python that requires numpy.
Comment 2 Ruslan Makhmatkhanov freebsd_committer 2018-07-30 17:57:19 UTC
(In reply to Kevin Zheng from comment #1)

+1, I also overcome that with adding following line /etc/libmap.conf

libgcc_s.so.1	/usr/local/lib/gcc6/libgcc_s.so.1
Comment 3 John W. O'Brien 2018-07-31 22:51:55 UTC
This smells like bug 201348 did.
Comment 4 Danilo G. Baio freebsd_committer 2020-03-16 22:50:51 UTC
Hi.
I've tested those imports after ports r528548 (www/py-notebook: Update to 6.0.3) and it seems fixed.
If this is still an issue, please reopen this bug.