Opened 4 months ago

Last modified 6 weeks 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 4 months ago by barracuda156

Okay, I dunno how to force the build system to acknowledge linking to legacy-support. Passing -Wl,-lMacportsLegacySupport to cflags does not help either.

comment:2 Changed 4 months ago by ryandesign (Ryan Carsten Schmidt)

Status: assignedaccepted
Summary: NetSurf needs legacysupport for _getlineNetSurf #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 4 months ago by ryandesign (Ryan Carsten Schmidt)

Summary: NetSurf #3.11: Undefined symbols: _getlineNetSurf @3.11: Undefined symbols: _getline

comment:4 in reply to:  2 Changed 4 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:5 Changed 6 weeks ago by barracuda156

Any update on this, Ryan?

comment:6 Changed 6 weeks ago by ryandesign (Ryan Carsten Schmidt)

Unfortunately it doesn't look like the developers have responded to the ticket I filed.

comment:7 in reply to:  6 Changed 6 weeks 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?

Note: See TracTickets for help on using tickets.