Warning message in macOS Mojave

Warning message in macOS Mojave

[Bill Findlay]

When I build my stuff under Mojave I get this warning:

> ld: warning: URGENT: building for OSX, but linking against dylib
> (/usr/lib/libSystem.dylib) built for (unknown). Note: This will be an error
> in the future.
It runs OK, but that is a little worrying.

-- 
Bill Findlay

Re: Warning message in macOS Mojave

[Simon Wright]

Bill Findlay <findlaybill@blueyonder.co.uk> writes:

> When I build my stuff under Mojave I get this warning:
>
>> ld: warning: URGENT: building for OSX, but linking against dylib
>> (/usr/lib/libSystem.dylib) built for (unknown). Note: This will be an error
>> in the future.
> It runs OK, but that is a little worrying.

I don't see that at all. (7.1.0, 8.0.0, CE)

libSystem.dylib should be a symlink to libSystem.B.dylib

Re: Warning message in macOS Mojave

[Bill Findlay]

On 25 Sep 2018, Simon Wright wrote
(in article <lypnx1o0rv.fsf@pushface.org>):

> Bill Findlay<findlaybill@blueyonder.co.uk>  writes:
>
> > When I build my stuff under Mojave I get this warning:
> >
> > > ld: warning: URGENT: building for OSX, but linking against dylib
> > > (/usr/lib/libSystem.dylib) built for (unknown). Note: This will be an error
> > > in the future.
> > It runs OK, but that is a little worrying.
>
> I don't see that at all. (7.1.0, 8.0.0, CE)
>
> libSystem.dylib should be a symlink to libSystem.B.dylib

High Sierra on my iMac:

-rwxr-xr-x 1 root wheel 650404 Jul 12:01 libSystem.B.dylib
lrwxr-xr-x 1 root wheel 1726 Sep 2017 libSystem.dylib -> libSystem.B.dylib

Mojave on my MBP:

-rwxr-xr-x 1 root wheel 6088021Sep 05:16 libSystem.B.dylib
lrwxr-xr-x 1 root wheel 1724Sep 22:30 libSystem.dylib -> libSystem.B.dylib

-- 
Bill Findlay

Re: Warning message in macOS Mojave

[Simon Wright]

Bill Findlay <findlaybill@blueyonder.co.uk> writes:

> Mojave on my MBP:
>
> -rwxr-xr-x 1 root wheel 6088021Sep 05:16 libSystem.B.dylib
> lrwxr-xr-x 1 root wheel 1724Sep 22:30 libSystem.dylib -> libSystem.B.dylib

I think there must be a tab/space missing there!

I see

-rwxr-xr-x  1 root  wheel  60880 21 Sep 05:16 /usr/lib/libSystem.B.dylib
lrwxr-xr-x  1 root  wheel     17 25 Sep 18:07 /usr/lib/libSystem.dylib -> libSystem.B.dylib

so that's the same.

What about the command line tools? I see

$ pkgutil --pkg-info=com.apple.pkg.CLTools_Executables
package-id: com.apple.pkg.CLTools_Executables
version: 10.0.0.0.1.1535735448
volume: /
location: /
install-time: 1537896473
groups: com.apple.FindSystemFiles.pkg-group

(which is the same, bar the install-time, as on my High Sierra MBP,
recently updated)

Re: Warning message in macOS Mojave

[Bill Findlay]

On 26 Sep 2018, Simon Wright wrote
(in article <lya7o436iq.fsf@pushface.org>):

> Bill Findlay<findlaybill@blueyonder.co.uk>  writes:
>
> > Mojave on my MBP:
> >
> > -rwxr-xr-x 1 root wheel 6088021Sep 05:16 libSystem.B.dylib
> > lrwxr-xr-x 1 root wheel 1724Sep 22:30 libSystem.dylib -> libSystem.B.dylib
>
> I think there must be a tab/space missing there!
Yes, this newsreader has strange properties.
It puts in newlines and takes out whitespace apparently at random.

> I see
>
> -rwxr-xr-x 1 root wheel 60880 21 Sep 05:16 /usr/lib/libSystem.B.dylib
> lrwxr-xr-x 1 root wheel 17 25 Sep 18:07 /usr/lib/libSystem.dylib ->
> libSystem.B.dylib
>
> so that's the same.
>
> What about the command line tools? I see
>
> $ pkgutil --pkg-info=com.apple.pkg.CLTools_Executables
> package-id: com.apple.pkg.CLTools_Executables
> version: 10.0.0.0.1.1535735448
> volume: /
> location: /
> install-time: 1537896473
> groups: com.apple.FindSystemFiles.pkg-group
>
> (which is the same, bar the install-time, as on my High Sierra MBP,
> recently updated)

I am using GNAT CE 2018, with a new unmodified Mojave install on my 2017 MBP.

> package-id: com.apple.pkg.CLTools_Executables version:
> 10.0.0.0.1.1535735448
> volume: /
> location: /
> install-time: 1537221714
> groups: com.apple.FindSystemFiles.pkg-group

The same. What about:

> $ cksum /usr/lib/libSystem.B.dylib
> 638756186 60880 /usr/lib/libSystem.B.dylib

I am using the build command:

> gnatmake -aI../Source -aO../Build -funwind-tables -gnatl12j96 -gnatw.e
> -gnatwD -gnatwH -gnatwP -gnatwT -gnatw.W -gnatw.B -gnatwC -gnatw.u -gnatyO
> -gnatw.Y -fdata-sections -ffunction-sections -gnatfn -mtune=native -O3 -flto
> -j0 ee9 -bargs -static -Sin -largs -Wl,-dead_strip -Wl,-dead_strip -flto

LTO has been dodgy in the past, but removing that option still results in the 
warning.

-- 
Bill Findlay

Re: Warning message in macOS Mojave

[Simon Wright]

Bill Findlay <findlaybill@blueyonder.co.uk> writes:

> I am using GNAT CE 2018, with a new unmodified Mojave install on my 2017 MBP.

I installed Mojave over High Sierra on an external USB.

> The same. What about:
>
>> $ cksum /usr/lib/libSystem.B.dylib
>> 638756186 60880 /usr/lib/libSystem.B.dylib

The same.

> I am using the build command:
>
>> gnatmake -aI../Source -aO../Build -funwind-tables -gnatl12j96
>> -gnatw.e -gnatwD -gnatwH -gnatwP -gnatwT -gnatw.W -gnatw.B -gnatwC
>> -gnatw.u -gnatyO -gnatw.Y -fdata-sections -ffunction-sections -gnatfn
>> -mtune=native -O3 -flto -j0 ee9 -bargs -static -Sin -largs
>> -Wl,-dead_strip -Wl,-dead_strip -flto
>
> LTO has been dodgy in the past, but removing that option still results
> in the warning.

Some build command! Remind me where your ee9 sources are? I've been
using just hello.adb for this check.

I don't think that -fdata-sections, -ffunction-sections are useful on
macOS, because Apple's clang ld doesn't support -gc-sections.

Re: Warning message in macOS Mojave

[Simon Wright]

Simon Wright <simon@pushface.org> writes:

> Remind me where your ee9 sources are

OK, Google was my friend

Re: Warning message in macOS Mojave

[Simon Wright]

Simon Wright <simon@pushface.org> writes:

> Simon Wright <simon@pushface.org> writes:
>
>> Remind me where your ee9 sources are
>
> OK, Google was my friend

Sorry to report that mk9 worked just fine, with both GCC 7.1.0 and GNAT
CE 2018. Not sure where to go from here.

Do you get the same problem with a plain hello.adb?

Re: Warning message in macOS Mojave

[Bill Findlay]

On 27 Sep 2018, Simon Wright wrote
(in article <lywor71aka.fsf@pushface.org>):

> Sorry to report that mk9 worked just fine,

Not normally cause for sorrow 8-)
> with both GCC 7.1.0 and GNAT
> CE 2018. Not sure where to go from here.
>
> Do you get the same problem with a plain hello.adb?

Simon, many thanks for this; it is much appreciated.

I:
* reinstalled GNAT CE 2018 in $HOME;
* deleted the copy in /opt;
* deleted the 2017 version in /opt;
* reinstalled the Command Line Tools;
* checked that the ld I was accessing was /usr/bin/ld, which is:
-rwxr-xr-x 1 root wheel 18272 21 Sep 05:16 ld * checked that the gnatmake I 
was accessing was /Users/wf/opt/GNAT/2018/bin/gnatmake, which is:
-rwxr-xr-x 1 wf staff 2388064 24 May 14:04 
/Users/wf/opt/GNAT/2018/bin/gnatmake
A trivial hello program still does evoke the warning.

The mystery deepens.

-- 
Bill Findlay

Re: Warning message in macOS Mojave

[Simon Wright]

There's this: https://github.com/golang/go/issues/27095
So you're not alone

Re: Warning message in macOS Mojave

[Bill Findlay]

On 27 Sep 2018, Simon Wright wrote
(in article <lysh1v0zo8.fsf@pushface.org>):

> There's this: https://github.com/golang/go/issues/27095
> So you're not alone

Interesting.

I tried replacing ld with the one from 10.13, but it made no difference.

-- 
Bill Findlay

Re: Warning message in macOS Mojave

[Bill Findlay]

On 27 Sep 2018, Bill Findlay wrote
(in article<0001HW.215D479300002848700003B092EF@news.individual.net>):

> On 27 Sep 2018, Simon Wright wrote
> (in article <lysh1v0zo8.fsf@pushface.org>):
>
> > There's this: https://github.com/golang/go/issues/27095
> > So you're not alone
>
> Interesting.
>
> I tried replacing ld with the one from 10.13, but it made no difference.

Deleting and reinstalling /Library/Developer/CommandLineTools
did the trick vis-a-vis the warning message. However I cannot
now compile a C program containing the line:

#include <stdlib.h>

getting:

../Build/kal3_source/kdf9.c:53:10: fatal error: stdlib.h: No such file or 
directory

I used to be able to solve this after a system update by reinstalling the 
command line tools!

-- 
Bill Findlay

Re: Warning message in macOS Mojave

[Simon Wright]

Bill Findlay <findlaybill@blueyonder.co.uk> writes:

> On 27 Sep 2018, Bill Findlay wrote
> (in article<0001HW.215D479300002848700003B092EF@news.individual.net>):
>
>> On 27 Sep 2018, Simon Wright wrote
>> (in article <lysh1v0zo8.fsf@pushface.org>):
>>
>> > There's this: https://github.com/golang/go/issues/27095
>> > So you're not alone
>>
>> Interesting.
>>
>> I tried replacing ld with the one from 10.13, but it made no
>> difference.
>
> Deleting and reinstalling /Library/Developer/CommandLineTools
> did the trick vis-a-vis the warning message. However I cannot
> now compile a C program containing the line:
>
> #include <stdlib.h>
>
> getting:
>
> ../Build/kal3_source/kdf9.c:53:10: fatal error: stdlib.h: No such file
> or directory
>
> I used to be able to solve this after a system update by reinstalling
> the command line tools!

I downloaded Command_Line_Tools_macOS_10.14_for_Xcode_10.dmg from
developer.apple.com/download/more and looked at it with Pacifist from
charlessoft.com; the /usr tree is in there. Perhaps try reinstalling? (I
don't see an option to uninstall).

Re: Warning message in macOS Mojave

[Bill Findlay]

On 30 Sep 2018, Simon Wright wrote
(in article <lyo9cf1lam.fsf@pushface.org>):

> Bill Findlay<findlaybill@blueyonder.co.uk>  writes:
>
> > On 27 Sep 2018, Bill Findlay wrote
> > (in article<0001HW.215D479300002848700003B092EF@news.individual.net>):
> >
> > > On 27 Sep 2018, Simon Wright wrote
> > > (in article <lysh1v0zo8.fsf@pushface.org>):
> > >
> > > > There's this: https://github.com/golang/go/issues/27095
> > > > So you're not alone
> > >
> > > Interesting.
> > >
> > > I tried replacing ld with the one from 10.13, but it made no
> > > difference.
> >
> > Deleting and reinstalling /Library/Developer/CommandLineTools
> > did the trick vis-a-vis the warning message. However I cannot
> > now compile a C program containing the line:
> >
> > #include <stdlib.h>
> >
> > getting:
> >
> > ../Build/kal3_source/kdf9.c:53:10: fatal error: stdlib.h: No such file
> > or directory
> >
> > I used to be able to solve this after a system update by reinstalling
> > the command line tools!
>
> I downloaded Command_Line_Tools_macOS_10.14_for_Xcode_10.dmg from
> developer.apple.com/download/more and looked at it with Pacifist from
> charlessoft.com; the /usr tree is in there. Perhaps try reinstalling? (I
> don't see an option to uninstall).

Thanks again, Simon.
Reinstalling Xcode seems to have sorted it out:
no disturbing warning, and C programs now compiling successfully.

-- 
Bill Findlay

Re: Warning message in macOS Mojave

[briot.emmanuel]

> I downloaded Command_Line_Tools_macOS_10.14_for_Xcode_10.dmg from
> developer.apple.com/download/more and looked at it with Pacifist from
> charlessoft.com; the /usr tree is in there. Perhaps try reinstalling? (I
> don't see an option to uninstall).

Simon,

I am always impressed by the amount of work you can put in answering people
on various forums ! (and I have tried a few times to be faster than you were on
stackoverflow, but never managed it). Impressive !

Emmanuel

Re: Warning message in macOS Mojave

[Simon Wright]

Bill Findlay <findlaybill@blueyonder.co.uk> writes:

> Thanks again, Simon.
> Reinstalling Xcode seems to have sorted it out:
> no disturbing warning, and C programs now compiling successfully.

Phew! Glad that hurdle's passed.

Re: Warning message in macOS Mojave

[Simon Wright]

briot.emmanuel@gmail.com writes:

> I am always impressed by the amount of work you can put in answering
> people on various forums ! (and I have tried a few times to be faster
> than you were on stackoverflow, but never managed it). Impressive !

:blush:

It helps to be retired :-)

Re: Warning message in macOS Mojave

[Bill Findlay]

On 1 Oct 2018, Simon Wright wrote
(in article <lyk1n12915.fsf@pushface.org>):

> Bill Findlay<findlaybill@blueyonder.co.uk>  writes:
>
> > Thanks again, Simon.
> > Reinstalling Xcode seems to have sorted it out:
> > no disturbing warning, and C programs now compiling successfully.
>
> Phew! Glad that hurdle's passed.

The strange thing is that re-installing the same (?) s/w twice did the trick.

I've heard of heisenbugs (not there if you look) and schroedingbugs
(there and not there at the same time).

Was this a fermibug (you have to do it twice to get back to the original 
state)?

-- 
Bill Findlay