Re: [Fink-users] Failed: phase compiling: gcc5-5.5.0-1 failed - different error from earlier thread

[Mark D. M. <qp...@qu...>]

On 11/16/2017 06:57 pm, Mark D. McKean wrote:
> On 11/16/2017 06:48 pm, Alexander Hansen wrote:
>>> On Nov 16, 2017, at 15:40, Mark D. McKean <qp...@qu...> wrote:
>>>
>>> On 11/16/2017 03:05 pm, Alexander Hansen wrote:
>>>>> On Nov 16, 2017, at 11:51, Mark D. McKean <qp...@qu...> wrote:
>>>>>>> qp...@qu...
>>>>>> My guess is that the stdio.h that it wants is one from the system, e.g. /usr/include/stdio.h .  You might check that that is present—a Fink build doesn’t necessarily automatically delve into the SDK directories.
>>>>>>
>>>>>> —akh
>>>>>>
>>>>>>
>>>>> Huh. /usr/include is empty except for a symlink to /opt/X11/include/X11, which doesn't contain stdio.h. Looking at my Time Machine backups, there doesn't appear to have been anything in this directory since I installed this hard drive six months ago. That don't seem right.
>>>>>
>>>>> I just went back and looked at my archived previous boot drive (running the same version of OS X), and its /usr/include appears to contain the usual assortment of files. I'm going to copy those over to my current boot drive and try the compile again.
>>>>>
>>>>> Mark D. McKean
>>>>>
>>>>> qp...@qu...
>>>> Ah, that would do it.  Most of our builds presume that /usr/include anded /usr/lib are populated.
>>>>
>>>> You might try reinstalling your Xcode Command line tools if that doesn’t work, just in case anything got missed.
>>>>
>>>> —akh
>>>>
>>> I would think that normally it would be safe to assume those are
>>> properly populated if you have the CLT installed. I'm curious as to how
>>> that didn't happen here, and why that hasn't affected any other compiles
>>> since the new drive. But I'll probably never know.
>>>
>>> At any rate, it looks like there is more missing, as the compile failed
>>> again, but with a different error: "ld: library not found for
>>> -ldylib1.10.5.o". So I'm going to reinstall the CLT like you suggested
>>> and try again.
>>>
>>> Thanks for picking up on that--I might never have considered checking
>>> /usr/include until much further into the process, based on the simple
>>> fact that having a functional Xcode.app and the CLT installed should
>>> mean those files are in the right place.
>>>
>>> Mark D. McKean
>>> qp...@qu...
>>>
>> After some checking, it appears that the file (and the rest of the headers there) comes from the DevSDK package.
>>
>> $ pkgutil --file-info /usr/include/stdio.h 
>> volume: /
>> path: /usr/include/stdio.h
>>
>> pkgid: com.apple.pkg.DevSDK
>> pkg-version: 10.12.4.1.1.1488873123
>> install-time: 1501008402
>> uid: 0
>> gid: 0
>> mode: 444
>>
>> pkgid: com.apple.pkg.DevSDK_OSX1012
>> pkg-version: 9.1.0.0.1.1508540944
>> install-time: 1510686483
>> uid: 0
>> gid: 0
>> mode: 444
>>
>> —akh
>>
>>
> Since reinstalling the CLT, mine comes up similar, though obviously an
> older version:
>
> $ pkgutil --file-info /usr/include/stdio.h
> volume: /
> path: /usr/include/stdio.h
>
> pkgid: com.apple.pkg.DevSDK_OSX1010
> pkg-version: 7.2.0.0.1.1447826929
> install-time: 1510864993
> uid: 0
> gid: 0
> mode: 444
>
> I've got the gcc5 update compiling now, so we'll see if it works this time.
>
> Mark D. McKean
> qp...@qu...
>
After roughly six hours, the compile completed successfully. So that was
the exact problem. I wouldn't have found it without your insight, so I
thank you profusely.

Mark D. McKean
qp...@qu...