Opened 10 months ago
Last modified 8 months ago
#69110 accepted defect
NetSurf @3.11: Undefined symbols: _getline
Reported by: | barracuda156 | Owned by: | ryandesign (Ryan Carsten Schmidt) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.8.1 |
Keywords: | leopard, snowleopard, tiger | Cc: | |
Port: | NetSurf |
Description
:info:build Undefined symbols: :info:build "_getline", referenced from: :info:build _fatmessages_read in cctMsPGv.o :info:build ld: symbol(s) not found
Simple addition of PG to the portfile did not help, however. Perhaps something prevents flags from being passed correctly.
Change History (7)
comment:1 Changed 10 months ago by barracuda156
comment:2 follow-up: 4 Changed 10 months ago by ryandesign (Ryan Carsten Schmidt)
Status: | assigned → accepted |
---|---|
Summary: | NetSurf needs legacysupport for _getline → NetSurf #3.11: Undefined symbols: _getline |
NetSurf is a browser intended to be portable to a wide range of systems so this strikes me as a problem upstream might want to know about so they can solve it. Reported here: https://bugs.netsurf-browser.org/mantis/view.php?id=2863
comment:3 Changed 10 months ago by ryandesign (Ryan Carsten Schmidt)
Summary: | NetSurf #3.11: Undefined symbols: _getline → NetSurf @3.11: Undefined symbols: _getline |
---|
comment:4 Changed 10 months ago by barracuda156
Replying to ryandesign:
NetSurf is a browser intended to be portable to a wide range of systems so this strikes me as a problem upstream might want to know about so they can solve it. Reported here: https://bugs.netsurf-browser.org/mantis/view.php?id=2863
Thank you!
I thought it could work for me for GitHub and GitLab, since I am having troubles with InterWebPPC and TenFourFox specifically for these sites, and it is very inconvenient to either switch to a laptop every time I just need to check something in an online repo or fetch the thing to use locally.
comment:6 follow-up: 7 Changed 8 months ago by ryandesign (Ryan Carsten Schmidt)
Unfortunately it doesn't look like the developers have responded to the ticket I filed.
comment:7 Changed 8 months ago by barracuda156
Replying to ryandesign:
Unfortunately it doesn't look like the developers have responded to the ticket I filed.
Can if be fixed on our end via LegacySupport or a direct patch?
Okay, I dunno how to force the build system to acknowledge linking to legacy-support. Passing
-Wl,-lMacportsLegacySupport
to cflags does not help either.