mango linking question

[Ken Cunningham]

Nothing important, we think.

When we first started building ports with the buildbot using BigSur, we built with the system of the time which was BigSur 11.2, so some of the builds were marked with that system as a floor.

We later decided hat it would be better to build against the lowest BigSur, so changed the builds to be against 11.0, so as to be compatible with all BigSur versions.

Not everything has been rebuilt, so there is still some 11.2 labelled code in there.

Ken

(it is possible, actually, that someone might install some of that 11.2 code on a BigSur 11.0 or 11.1 system and something might not work right. That has not yet been reported, and not many are likely hanging back on < 11.2 any more, so we haven't gone through rebuilding it all. In due course, everything will get rebuilt and then this error should no longer appear. 

It is also possible that something good might happen if the port was built against - say - 11.6 that can't happen if the build is forced to be 11.0 compatible. That also has not happened yet as far as we know, so we are watching for that at the moment).

K

> On Sep 30, 2021, at 11:27 AM, Langer, Stephen A. (Fed) via macports-users <macports-users at lists.macports.org> wrote:
> 
> Hi --
> 
> What do these messages mean, and do I need to worry about them?  They occur when linking a program with clang++.
> 
> % /usr/bin/clang++ -L/opt/local/lib ... something.o ... -lpangocairo-1.0 -lpango-1.0 ... -o something.so
> 
> ld: warning: dylib (/opt/local/lib/libpangocairo-1.0.dylib) was built for newer macOS version (11.2) than being linked (11.0)
> ld: warning: dylib (/opt/local/lib/libpango-1.0.dylib) was built for newer macOS version (11.2) than being linked (11.0)
> 
> I'm using Big Sur 11.6 with Xcode 13.0.  Macports is up to date, and so is pango.
> 
> % port installed pango
> The following ports are currently installed:
>  pango @1.42.4_3+quartz+x11 (active)
> 
> Thanks.
> -- Steve
>