Opened 4 years ago

Last modified 2 years ago

#62675 assigned defect

wgrib2: ld: library not found for -lMacportsLegacySupport

Reported by: ryandesign (Ryan Carsten Schmidt) Owned by: tenomoto (Takeshi Enomoto)
Priority: Normal Milestone:
Component: ports Version: 2.6.4
Keywords: Cc: kencu (Ken), evanmiller (Evan Miller), cooljeanius (Eric Gallager)
Port: wgrib2

Description

​https://build.macports.org/builders/ports-10.11_x86_64-builder/builds/138652/steps/install-port/logs/stdio 

ld: library not found for -lMacportsLegacySupport

I don't see why legacy support is being used on 10.11 when the portfile says only to use it on 10.6 and earlier.

Perhaps a bad interaction with the compilers portgroup?

I wonder if using legacysupport 1.1 instead of legacysupport 1.0 would help.

Change History (3)

comment:1 Changed 3 years ago by evanmiller (Evan Miller)

Cc: evanmiller added

comment:2 Changed 3 years ago by evanmiller (Evan Miller)

It looks like legacysupport 1.0 has faulty logic that always adds legacy support for 10.12 and earlier:

​https://github.com/macports/macports-ports/blob/88bdf88e7b20351fceac37d7d75ceb7641b29b92/_resources/port1.0/group/legacysupport-1.0.tcl#L83-L89

The issue is that when add_legacysupport is first called, legacy.newest_darwin_requires_legacy is the default value (16) and so legacy support is added on 10.11.

When add_legacysupport is called a second time via register_callback, legacy.newest_darwin_requires_legacy has the correct value (10 in this case) but the build environment is not actually modified to remove legacy support.

I suggest upgrading the PG to 1.1.

comment:3 Changed 2 years ago by cooljeanius (Eric Gallager)

Cc: cooljeanius added
Note: See TracTickets for help on using tickets.