Re: [Fink-devel] Fink and 10.11?

[Alexander Hansen]

> On Oct 1, 2015, at 13:35, Kevin Horton  wrote:
> 
> I think fink 0.39.0 supports OS X 10.11, but I haven’t seen any official info 
> to confirm this.  I’d like to update from OS X 10.10 to 10.11 soon.  What is 
> the official path to do this?
> 
> Thanks,
> 
> Kevin Horton
> Ottawa, Canada

There’s no info because website updates have a fairly hideous workflow for me 
to accomplish while at work. :-)

The official best upgrade path is to follow essentially the same steps as in 
http://www.finkproject.org/download/10.10-upgrade.php?phpLang=en 
, with the 
following addenda:

1) Unchanged
1a)  Run “fink selfupdate” again because we’ve switched the distribution tree.
2) Unchanged
3) You want Xcode 7 or later.
4) Unchanged
5) Unchanged
6) Unchanged
7)  10.10 and 10.11 have the same Perl,  so you don’t need to do the optional 
Perl install.  The passwd* optional step still applies.

-- 
Alexander Hansen, Ph.D.
Fink User Liaison

--
___
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel

[Fink-devel] Fink and 10.11?

[Kevin Horton]

I think fink 0.39.0 supports OS X 10.11, but I haven’t seen any official info 
to confirm this.  I’d like to update from OS X 10.10 to 10.11 soon.  What is 
the official path to do this?

Thanks,

Kevin Horton
Ottawa, Canada
--
___
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel

Re: [Fink-devel] A few 10.11 glitches and possible workarounds

[Jack Howarth]

On Thu, Oct 1, 2015 at 2:41 PM, Alexander Hansen <
alexanderk.han...@gmail.com> wrote:

>
> On Oct 1, 2015, at 11:24, Jack Howarth  wrote:
>
>
>
> On Thu, Oct 1, 2015 at 12:02 PM, Jack Howarth 
> wrote:
>
>>
>>
>> On Thu, Oct 1, 2015 at 12:33 AM, William G. Scott 
>> wrote:
>>
>>> In the course of building some of my packages, a few dependencies failed
>>> to compile, requiring minor tweaks:
>>>
>>> gtk+2  — I had to change to UseMaxBuildJobs: false
>>> libvpx14  — I had to change to UseMaxBuildJobs: false
>>>
>>
>> Bill,
>>  I suspect you have the fink make package installed, no? If so, the
>> failures should have been accompanied with an error message of the form...
>>
>> make: INTERNAL: Exiting with 1 jobserver tokens available; should be 8!
>>
>> This breakage in the parallel make of fink make impacts a slew of fink
>> package builds on machines with more than 2 cores (eg the cmake, libcurl4,
>> texlive-base, etc builds).
>> A better fix would be to revert your package back to UseMaxBuildJobs:
>> true but hard code' /usr/bin/make' rather than just 'make'.
>> Jack
>> ps The issue seems to be limited to running fink make from within perl
>> under fink. I've not been able to reproduce the build failures outside of
>> fink or with just within perl itself.
>>
>
> Actually, I never saw a problem building gtk+2 on a dual quad-core MacPro
> but this re-enforces my suspicion that the problem with fink make is a
> threading race condition that will selectively trigger depending on the
> number of cores and processor speed of a given machine (meaning that all
> parallel builds under fink make on 10.11 are fragile). Perhaps a better fix
> would be to have fink conditionally use /usr/bin/make rather than make for
> the CompileScript's default_script when executed on 10.11. This would at
> least automatically solve the issue for all packages using
> %{default_script}.
>
>
>
> We can default to /usr/bin/make on 10.9-10.11 unconditionally and let
> individual packages that need fink’s make override that in their
> CompileScripts.  That’d be simpler, and more consistent with our general
> practices with regard to build tools.
>
>
It would be a good idea to also modify the fink make package to build
with the g-prefix and implement the make-default split-off to provide the
make symlink to gmake. Then just note that usage of make-default on 10.11
is for masochists only.

Then we can add a conditional if Apple decides to stop shipping a
> /usr/bin/make with Xcode.
> --
> Alexander Hansen, Ph.D.
> Fink User Liaison
>
>
>
> --
>
> ___
> Fink-devel mailing list
> Fink-devel@lists.sourceforge.net
> List archive:
> http://news.gmane.org/gmane.os.apple.fink.devel
> Subscription management:
> https://lists.sourceforge.net/lists/listinfo/fink-devel
>
>
--
___
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel

Re: [Fink-devel] A few 10.11 glitches and possible workarounds

[Alexander Hansen]

> On Oct 1, 2015, at 11:41, Alexander Hansen  
> wrote:
> 
>> 
>> On Oct 1, 2015, at 11:24, Jack Howarth > > wrote:
>> 
>> 
>> 
>> On Thu, Oct 1, 2015 at 12:02 PM, Jack Howarth > > wrote:
>> 
>> 
>> On Thu, Oct 1, 2015 at 12:33 AM, William G. Scott > > wrote:
>> In the course of building some of my packages, a few dependencies failed to 
>> compile, requiring minor tweaks:
>> 
>> gtk+2  — I had to change to UseMaxBuildJobs: false
>> libvpx14  — I had to change to UseMaxBuildJobs: false
>> 
>> Bill,
>>  I suspect you have the fink make package installed, no? If so, the 
>> failures should have been accompanied with an error message of the form...
>> 
>> make: INTERNAL: Exiting with 1 jobserver tokens available; should be 8!
>> 
>> This breakage in the parallel make of fink make impacts a slew of fink 
>> package builds on machines with more than 2 cores (eg the cmake, libcurl4, 
>> texlive-base, etc builds).
>> A better fix would be to revert your package back to UseMaxBuildJobs: true 
>> but hard code' /usr/bin/make' rather than just 'make'.
>> Jack
>> ps The issue seems to be limited to running fink make from within perl under 
>> fink. I've not been able to reproduce the build failures outside of fink or 
>> with just within perl itself.
>> 
>> Actually, I never saw a problem building gtk+2 on a dual quad-core MacPro 
>> but this re-enforces my suspicion that the problem with fink make is a 
>> threading race condition that will selectively trigger depending on the 
>> number of cores and processor speed of a given machine (meaning that all 
>> parallel builds under fink make on 10.11 are fragile). Perhaps a better fix 
>> would be to have fink conditionally use /usr/bin/make rather than make for 
>> the CompileScript's default_script when executed on 10.11. This would at 
>> least automatically solve the issue for all packages using %{default_script}.
>>  
> 
> We can default to /usr/bin/make on 10.9-10.11 unconditionally and let 
> individual packages that need fink’s make override that in their 
> CompileScripts.  That’d be simpler, and more consistent with our general 
> practices with regard to build tools.
> 
> Then we can add a conditional if Apple decides to stop shipping a 
> /usr/bin/make with Xcode. 
> -- 
> Alexander Hansen, Ph.D.
> Fink User Liaison

I just created a default-to-usr-bin-make branch off of the fink-0.39.x release 
tree and an accompanying pull request:

https://github.com/fink/fink/pull/125 

People who are interested in testing whether defaulting to /usr/bin/make has 
any unforeseen consequences can do so by checking out that branch and using 
inject.pl to install it.  

Because this is branched from the release branch, a selfupdate will still bring 
you a new release fink-0.39.x when one comes out.

-- 
Alexander Hansen, Ph.D.
Fink User Liaison

--
___
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel

Re: [Fink-devel] A few 10.11 glitches and possible workarounds

[Alexander Hansen]

> On Oct 1, 2015, at 11:24, Jack Howarth  wrote:
> 
> 
> 
> On Thu, Oct 1, 2015 at 12:02 PM, Jack Howarth  > wrote:
> 
> 
> On Thu, Oct 1, 2015 at 12:33 AM, William G. Scott  > wrote:
> In the course of building some of my packages, a few dependencies failed to 
> compile, requiring minor tweaks:
> 
> gtk+2  — I had to change to UseMaxBuildJobs: false
> libvpx14  — I had to change to UseMaxBuildJobs: false
> 
> Bill,
>  I suspect you have the fink make package installed, no? If so, the 
> failures should have been accompanied with an error message of the form...
> 
> make: INTERNAL: Exiting with 1 jobserver tokens available; should be 8!
> 
> This breakage in the parallel make of fink make impacts a slew of fink 
> package builds on machines with more than 2 cores (eg the cmake, libcurl4, 
> texlive-base, etc builds).
> A better fix would be to revert your package back to UseMaxBuildJobs: true 
> but hard code' /usr/bin/make' rather than just 'make'.
> Jack
> ps The issue seems to be limited to running fink make from within perl under 
> fink. I've not been able to reproduce the build failures outside of fink or 
> with just within perl itself.
> 
> Actually, I never saw a problem building gtk+2 on a dual quad-core MacPro but 
> this re-enforces my suspicion that the problem with fink make is a threading 
> race condition that will selectively trigger depending on the number of cores 
> and processor speed of a given machine (meaning that all parallel builds 
> under fink make on 10.11 are fragile). Perhaps a better fix would be to have 
> fink conditionally use /usr/bin/make rather than make for the CompileScript's 
> default_script when executed on 10.11. This would at least automatically 
> solve the issue for all packages using %{default_script}.
>  

We can default to /usr/bin/make on 10.9-10.11 unconditionally and let 
individual packages that need fink’s make override that in their 
CompileScripts.  That’d be simpler, and more consistent with our general 
practices with regard to build tools.

Then we can add a conditional if Apple decides to stop shipping a /usr/bin/make 
with Xcode. 
-- 
Alexander Hansen, Ph.D.
Fink User Liaison

--
___
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel

Re: [Fink-devel] A few 10.11 glitches and possible workarounds

[Jack Howarth]

On Thu, Oct 1, 2015 at 12:02 PM, Jack Howarth 
wrote:

>
>
> On Thu, Oct 1, 2015 at 12:33 AM, William G. Scott 
> wrote:
>
>> In the course of building some of my packages, a few dependencies failed
>> to compile, requiring minor tweaks:
>>
>> gtk+2  — I had to change to UseMaxBuildJobs: false
>> libvpx14  — I had to change to UseMaxBuildJobs: false
>>
>
> Bill,
>  I suspect you have the fink make package installed, no? If so, the
> failures should have been accompanied with an error message of the form...
>
> make: INTERNAL: Exiting with 1 jobserver tokens available; should be 8!
>
> This breakage in the parallel make of fink make impacts a slew of fink
> package builds on machines with more than 2 cores (eg the cmake, libcurl4,
> texlive-base, etc builds).
> A better fix would be to revert your package back to UseMaxBuildJobs: true
> but hard code' /usr/bin/make' rather than just 'make'.
> Jack
> ps The issue seems to be limited to running fink make from within perl
> under fink. I've not been able to reproduce the build failures outside of
> fink or with just within perl itself.
>

Actually, I never saw a problem building gtk+2 on a dual quad-core MacPro
but this re-enforces my suspicion that the problem with fink make is a
threading race condition that will selectively trigger depending on the
number of cores and processor speed of a given machine (meaning that all
parallel builds under fink make on 10.11 are fragile). Perhaps a better fix
would be to have fink conditionally use /usr/bin/make rather than make for
the CompileScript's default_script when executed on 10.11. This would at
least automatically solve the issue for all packages using
%{default_script}.


>
> Also, $X11_BASE_DIR doesn’t seem to get set.
>>
>>
>> Bill Scott
>>
>>
>>
>>
>> --
>> ___
>> Fink-devel mailing list
>> Fink-devel@lists.sourceforge.net
>> List archive:
>> http://news.gmane.org/gmane.os.apple.fink.devel
>> Subscription management:
>> https://lists.sourceforge.net/lists/listinfo/fink-devel
>>
>
>
--
___
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel

[Fink-devel] fink-0.39 has gone live

[Alexander Hansen]

fink-0.39 switches to a new distribution tree for 10.9+.  

Please use the new 10.9-libcxx tree if you want your package updates to be 
applied on 10.9 and later.  The 10.7 tree remains as-is for 10.7 and 10.8 
packaging.
-- 
Alexander Hansen, Ph.D.
Fink User Liaison


--
___
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel

Re: [Fink-devel] A few 10.11 glitches and possible workarounds

[Jack Howarth]

On Thu, Oct 1, 2015 at 12:33 AM, William G. Scott  wrote:

> In the course of building some of my packages, a few dependencies failed
> to compile, requiring minor tweaks:
>
> gtk+2  — I had to change to UseMaxBuildJobs: false
> libvpx14  — I had to change to UseMaxBuildJobs: false
>

Bill,
 I suspect you have the fink make package installed, no? If so, the
failures should have been accompanied with an error message of the form...

make: INTERNAL: Exiting with 1 jobserver tokens available; should be 8!

This breakage in the parallel make of fink make impacts a slew of fink
package builds on machines with more than 2 cores (eg the cmake, libcurl4,
texlive-base, etc builds).
A better fix would be to revert your package back to UseMaxBuildJobs: true
but hard code' /usr/bin/make' rather than just 'make'.
Jack
ps The issue seems to be limited to running fink make from within perl
under fink. I've not been able to reproduce the build failures outside of
fink or with just within perl itself.

Also, $X11_BASE_DIR doesn’t seem to get set.
>
>
> Bill Scott
>
>
>
>
> --
> ___
> Fink-devel mailing list
> Fink-devel@lists.sourceforge.net
> List archive:
> http://news.gmane.org/gmane.os.apple.fink.devel
> Subscription management:
> https://lists.sourceforge.net/lists/listinfo/fink-devel
>
--
___
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel

Re: [Fink-devel] A few 10.11 glitches and possible workarounds

[William G. Scott]

> On Oct 1, 2015, at 8:01 AM, Alexander Hansen  
> wrote:
> 
> 
>> On Oct 1, 2015, at 07:59, Hanspeter Niederstrasser  
>> wrote:
>> 
>> On Thu, October 1, 2015 9:17 am, William G. Scott wrote:
>>> 
 On Oct 1, 2015, at 4:16 AM, Hanspeter Niederstrasser
  wrote:
 
 What happens if you run
 
 . /sw/sbin/fink-buildenv-helper.sh
 
 from a new terminal window?  If it immediately exits (say with a
 MACOSX_DEPLOYMENT_TARGET failure), set MACOSX_DEPLOYMENT_TARGET to 10.11
 in your shell, and try running fink-buildenv-helper.sh again.
 
 Hanspeter
>>> 
>>> OK, that was the problem, and manually setting $MACOSX_DEPLOYMENT_TARGET
>>> worked.  (I didn’t explicitly check to see if that solved the problem
>>> within the package I was having trouble with, but the output suggests that
>>> it would).  To my knowledge, I never explicitly set
>>> $MACOSX_DEPLOYMENT_TARGET in previous OS X versions (i.e., the same
>>> package compiles without incident on 10.10, 10.9, 10.6).  This happens
>>> with bash, tcsh and zsh.
>> 
>> There are two mismatch checks in fink-buildenv-helper.sh.  One checks that
>> your OS version matches the MACOSX_DEPLOYMENT_TARGET that Fink sets during
>> a build. The other check is to make sure that the available SDK and
>> MACOSX_DEPLOYMENT_TARGET match.  But 10.11 now also uses the 10.10 SDK, so
>> I need to release a new helper script that says 10 equals 11.
>> 
>> Hanspeter
>> 
>> -- 
>> More agile than a turtle, stronger than a mouse, nobler than a lettuce
>> 
>> 
> 
> Isn’t it the other way around?  I thought the case was that 10.10 uses the 
> 10.11 SDK for Xcode 7.
> 


May I suggest changing all instances of “exit 1” to “return 1”  in  
/sw/lib/fink-buildenv-modules/base.sh so that the shell itself doesn’t exit 
when the file is sourced rather than executed?



--
___
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel

Re: [Fink-devel] A few 10.11 glitches and possible workarounds

[Alexander Hansen]

> On Oct 1, 2015, at 07:59, Hanspeter Niederstrasser  
> wrote:
> 
> On Thu, October 1, 2015 9:17 am, William G. Scott wrote:
>> 
>>> On Oct 1, 2015, at 4:16 AM, Hanspeter Niederstrasser
>>>  wrote:
>>> 
>>> What happens if you run
>>> 
>>> . /sw/sbin/fink-buildenv-helper.sh
>>> 
>>> from a new terminal window?  If it immediately exits (say with a
>>> MACOSX_DEPLOYMENT_TARGET failure), set MACOSX_DEPLOYMENT_TARGET to 10.11
>>> in your shell, and try running fink-buildenv-helper.sh again.
>>> 
>>> Hanspeter
>> 
>> OK, that was the problem, and manually setting $MACOSX_DEPLOYMENT_TARGET
>> worked.  (I didn’t explicitly check to see if that solved the problem
>> within the package I was having trouble with, but the output suggests that
>> it would).  To my knowledge, I never explicitly set
>> $MACOSX_DEPLOYMENT_TARGET in previous OS X versions (i.e., the same
>> package compiles without incident on 10.10, 10.9, 10.6).  This happens
>> with bash, tcsh and zsh.
> 
> There are two mismatch checks in fink-buildenv-helper.sh.  One checks that
> your OS version matches the MACOSX_DEPLOYMENT_TARGET that Fink sets during
> a build. The other check is to make sure that the available SDK and
> MACOSX_DEPLOYMENT_TARGET match.  But 10.11 now also uses the 10.10 SDK, so
> I need to release a new helper script that says 10 equals 11.
> 
> Hanspeter
> 
> -- 
> More agile than a turtle, stronger than a mouse, nobler than a lettuce
> 
> 

Isn’t it the other way around?  I thought the case was that 10.10 uses the 
10.11 SDK for Xcode 7.


--
___
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel

Re: [Fink-devel] A few 10.11 glitches and possible workarounds

[Hanspeter Niederstrasser]

On Thu, October 1, 2015 9:17 am, William G. Scott wrote:
>
>> On Oct 1, 2015, at 4:16 AM, Hanspeter Niederstrasser
>>  wrote:
>>
>> What happens if you run
>>
>> . /sw/sbin/fink-buildenv-helper.sh
>>
>> from a new terminal window?  If it immediately exits (say with a
>> MACOSX_DEPLOYMENT_TARGET failure), set MACOSX_DEPLOYMENT_TARGET to 10.11
>> in your shell, and try running fink-buildenv-helper.sh again.
>>
>> Hanspeter
>
> OK, that was the problem, and manually setting $MACOSX_DEPLOYMENT_TARGET
> worked.  (I didn’t explicitly check to see if that solved the problem
> within the package I was having trouble with, but the output suggests that
> it would).  To my knowledge, I never explicitly set
> $MACOSX_DEPLOYMENT_TARGET in previous OS X versions (i.e., the same
> package compiles without incident on 10.10, 10.9, 10.6).  This happens
> with bash, tcsh and zsh.

There are two mismatch checks in fink-buildenv-helper.sh.  One checks that
your OS version matches the MACOSX_DEPLOYMENT_TARGET that Fink sets during
a build. The other check is to make sure that the available SDK and
MACOSX_DEPLOYMENT_TARGET match.  But 10.11 now also uses the 10.10 SDK, so
I need to release a new helper script that says 10 equals 11.

Hanspeter

-- 
More agile than a turtle, stronger than a mouse, nobler than a lettuce


--
___
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel

Re: [Fink-devel] A few 10.11 glitches and possible workarounds

[William G. Scott]

> On Oct 1, 2015, at 4:16 AM, Hanspeter Niederstrasser  
> wrote:
> 
> What happens if you run
> 
> . /sw/sbin/fink-buildenv-helper.sh
> 
> from a new terminal window?  If it immediately exits (say with a 
> MACOSX_DEPLOYMENT_TARGET failure), set MACOSX_DEPLOYMENT_TARGET to 10.11 in 
> your shell, and try running fink-buildenv-helper.sh again.
> 
> Hanspeter

OK, that was the problem, and manually setting $MACOSX_DEPLOYMENT_TARGET 
worked.  (I didn’t explicitly check to see if that solved the problem within 
the package I was having trouble with, but the output suggests that it would).  
To my knowledge, I never explicitly set $MACOSX_DEPLOYMENT_TARGET in previous 
OS X versions (i.e., the same package compiles without incident on 10.10, 10.9, 
10.6).  This happens with bash, tcsh and zsh.

[BTW, running  /sw/sbin/fink-buildenv-helper.sh  as an executable gives me a 
meaningful error.  Sourcing it   .  /sw/sbin/fink-buildenv-helper.sh  just 
exits the shell. ]
--
___
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel

Re: [Fink-devel] A few 10.11 glitches and possible workarounds

[Hanspeter Niederstrasser]

On 9/30/2015 11:33 PM, William G. Scott wrote:
> In the course of building some of my packages, a few dependencies failed to 
> compile, requiring minor tweaks:
>
> gtk+2  — I had to change to UseMaxBuildJobs: false
> libvpx14  — I had to change to UseMaxBuildJobs: false
> fftw   — I had to change it to build with gcc5
>
> Also, $X11_BASE_DIR doesn’t seem to get set.

What happens if you run

. /sw/sbin/fink-buildenv-helper.sh

from a new terminal window?  If it immediately exits (say with a 
MACOSX_DEPLOYMENT_TARGET failure), set MACOSX_DEPLOYMENT_TARGET to 10.11 
in your shell, and try running fink-buildenv-helper.sh again.

Hanspeter


--
___
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel