Re: [Fink-users] Build failure in icon-9.5.0-2 on Yosemite

2015-04-28 Thread Mark D. McKean
On 04/26/2015 11:58 am, Alexander Hansen wrote:
snip
 After looking inside xpmP.h, I realized it was trying to find the
 X11 includes directly in the default location of /usr/include/X11.

 This has ceased to exist on OS X as of 10.8.  /usr/include/X11 was a
 convenience symlink and the Xquartz developers decided to get rid of
 it, apparently.

It must have been removed when Apple dropped support for X11 as part of 
the OS X install. Maybe Apple requested the XQuartz project not use it? 
Not important, of course, but I frequently wonder about things that 
aren't important. :-)

snip
 A check for whether those headers are in the right place, and
 creating the symlink if not, should probably be added to the patch
 file for icon.

 Absolutely not.  We DON”T mess around in the system area if we can
 avoid it.  If you want to use some other packaging system that is
 willing to screw you over, that’s your business, but we’re not going
 to do that.

Whoa, calm down. Did I stumble into a touchy subject? I didn't realize 
that /usr was considered a verboten system area for Fink, since most 
Unix packages installed outside a package manager have no qualms 
whatsoever about adding things there. It's not as though I suggested 
removing or replacing something there.

As for some other packaging system screwing me over, that's an 
inappropriate assertion that appears to come from an incorrect 
assumption. No other package manager was responsible for creating that 
symlink--I created it myself based on the educated guess that a new 
symlink where there was nothing before wouldn't cause any immediate 
problems and was unlikely to cause any long-term ones unless an Apple 
update at some point in the future removed it. I didn't even get the 
idea from some other installer; as I said, that symlink is not present 
on my Mavericks drive either, where I had successfully installed 
Homebrew's icon package.

I suggested the symlink because it seemed to me to be the simplest and 
most certain solution. It was also the only way I could test my 
hypothesis myself, since I don't know enough about how Fink packages are 
set up to make an appropriate change from that side. I didn't expect 
resolving that problem to simply uncover a different one that I couldn't 
resolve, so I figured I could make the change, build the package, and be 
on my way.

 From a Fink standpoint, the best thing to do is to make sure that
 -I/opt/X11/include shows up on the compiler lines.

With the symlink out of the question, that certainly makes sense. I'm 
not sure why you couldn't have just said that in the first place, and 
left out the smackdown.

snip
 cc -arch i386  -L/sw/lib -o icont tunix.o tglobals.o util.o
 trans.o tcode.o tlex.o lnklist.o tparse.o tsym.o tmem.o tree.o
 link.o lglob.o lcode.o llex.o lmem.o lsym.o opcode.o
 ../common/long.o ../common/getopt.o ../common/alloc.o
 ../common/filepart.o ../common/strtbl.o ../common/ipp.o
 ../common/munix.o cc -arch i386  -L/sw/lib -o icont tunix.o
 tglobals.o util.o trans.o tcode.o tlex.o lnklist.o tparse.o tsym.o
 tmem.o tree.o link.o lglob.o lcode.o llex.o lmem.o lsym.o opcode.o
 ../common/long.o ../common/getopt.o ../common/alloc.o
 ../common/filepart.o ../common/strtbl.o ../common/ipp.o
 ../common/munix.o cp icont ../../bin cp icont ../../bin strip
 ../../bin/icont strip ../../bin/icont (cd ../../bin; rm -f icon
 icon.exe; ln -s icont icon) (cd ../../bin; rm -f icon icon.exe; ln
 -s icont icon) ln: icon: File exists make[1]: *** [icont] Error 1
 cd src/runtime;
 /Applications/Xcode.app/Contents/Developer/usr/bin/make make: ***
 [bin/icont] Error 2 make: *** Waiting for unfinished jobs

 This was the fatal error.  You’re building with multiple jobs and it
 took a while for the other threads to catch up.

I figured that was why the build continued. That doesn't tell me what 
makes this a fatal error.

 This is one reason why we ask people to try again with a single build
 job before submitting their error messages.

I usually do. I didn't this time because I was dealing with multiple 
errors and trying to figure out what I could fix, and I didn't feel like 
waiting through yet another compile attempt before I could finish that 
email. By that time it was already really late. My apologies. I have 
since retried it with build jobs set to 1.

 One other thing I noticed: while investigating the problem, I
 noticed that the info file for icon specifies a build configuration
 that forces a 32-bit build on a 64-bit system:
snip
 The most significant change I noticed was that the error I detailed
 above was not present this time, but shortly before that point,
 this error appeared:

 strip ixhdr.hdr error:
 /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/strip:
can't move temporary file:
 /sw/src/fink.build/icon-9.5.0-2/icon-v950src/src/icont/ixhdr.hdr.strip
to input file:
 /sw/src/fink.build/icon-9.5.0-2/icon-v950src/src/icont/ixhdr.hdr
 (No such file or directory) 

Re: [Fink-users] Build failure in icon-9.5.0-2 on Yosemite

2015-04-28 Thread Alexander Hansen

 On Apr 28, 2015, at 18:38, Mark D. McKean qpa...@quantumpanda.com wrote:
 
 On 04/26/2015 11:58 am, Alexander Hansen wrote:
 snip
 After looking inside xpmP.h, I realized it was trying to find the
 X11 includes directly in the default location of /usr/include/X11.
 
 This has ceased to exist on OS X as of 10.8.  /usr/include/X11 was a
 convenience symlink and the Xquartz developers decided to get rid of
 it, apparently.
 
 It must have been removed when Apple dropped support for X11 as part of 
 the OS X install. Maybe Apple requested the XQuartz project not use it? 
 Not important, of course, but I frequently wonder about things that 
 aren't important. :-)
 
 snip
 A check for whether those headers are in the right place, and
 creating the symlink if not, should probably be added to the patch
 file for icon.
 
 Absolutely not.  We DON”T mess around in the system area if we can
 avoid it.  If you want to use some other packaging system that is
 willing to screw you over, that’s your business, but we’re not going
 to do that.
 
 Whoa, calm down. Did I stumble into a touchy subject? I didn't realize 
 that /usr was considered a verboten system area for Fink, since most 
 Unix packages installed outside a package manager have no qualms 
 whatsoever about adding things there. It's not as though I suggested 
 removing or replacing something there.
 
 As for some other packaging system screwing me over, that's an 
 inappropriate assertion that appears to come from an incorrect 
 assumption. No other package manager was responsible for creating that 
 symlink--I created it myself based on the educated guess that a new 
 symlink where there was nothing before wouldn't cause any immediate 
 problems and was unlikely to cause any long-term ones unless an Apple 
 update at some point in the future removed it. I didn't even get the 
 idea from some other installer; as I said, that symlink is not present 
 on my Mavericks drive either, where I had successfully installed 
 Homebrew's icon package.
 
 I suggested the symlink because it seemed to me to be the simplest and 
 most certain solution. It was also the only way I could test my 
 hypothesis myself, since I don't know enough about how Fink packages are 
 set up to make an appropriate change from that side. I didn't expect 
 resolving that problem to simply uncover a different one that I couldn't 
 resolve, so I figured I could make the change, build the package, and be 
 on my way.
 
 From a Fink standpoint, the best thing to do is to make sure that
 -I/opt/X11/include shows up on the compiler lines.
 
 With the symlink out of the question, that certainly makes sense. I'm 
 not sure why you couldn't have just said that in the first place, and 
 left out the smackdown.
 
 snip
 cc -arch i386  -L/sw/lib -o icont tunix.o tglobals.o util.o
 trans.o tcode.o tlex.o lnklist.o tparse.o tsym.o tmem.o tree.o
 link.o lglob.o lcode.o llex.o lmem.o lsym.o opcode.o
 ../common/long.o ../common/getopt.o ../common/alloc.o
 ../common/filepart.o ../common/strtbl.o ../common/ipp.o
 ../common/munix.o cc -arch i386  -L/sw/lib -o icont tunix.o
 tglobals.o util.o trans.o tcode.o tlex.o lnklist.o tparse.o tsym.o
 tmem.o tree.o link.o lglob.o lcode.o llex.o lmem.o lsym.o opcode.o
 ../common/long.o ../common/getopt.o ../common/alloc.o
 ../common/filepart.o ../common/strtbl.o ../common/ipp.o
 ../common/munix.o cp icont ../../bin cp icont ../../bin strip
 ../../bin/icont strip ../../bin/icont (cd ../../bin; rm -f icon
 icon.exe; ln -s icont icon) (cd ../../bin; rm -f icon icon.exe; ln
 -s icont icon) ln: icon: File exists make[1]: *** [icont] Error 1
 cd src/runtime;
 /Applications/Xcode.app/Contents/Developer/usr/bin/make make: ***
 [bin/icont] Error 2 make: *** Waiting for unfinished jobs
 
 This was the fatal error.  You’re building with multiple jobs and it
 took a while for the other threads to catch up.
 
 I figured that was why the build continued. That doesn't tell me what 
 makes this a fatal error.
 
 This is one reason why we ask people to try again with a single build
 job before submitting their error messages.
 
 I usually do. I didn't this time because I was dealing with multiple 
 errors and trying to figure out what I could fix, and I didn't feel like 
 waiting through yet another compile attempt before I could finish that 
 email. By that time it was already really late. My apologies. I have 
 since retried it with build jobs set to 1.
 
 One other thing I noticed: while investigating the problem, I
 noticed that the info file for icon specifies a build configuration
 that forces a 32-bit build on a 64-bit system:
 snip
 The most significant change I noticed was that the error I detailed
 above was not present this time, but shortly before that point,
 this error appeared:
 
 strip ixhdr.hdr error:
 /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/strip:
 can't move temporary file:
 

Re: [Fink-users] Installation problems

2015-04-28 Thread Alexander Hansen

 On Apr 28, 2015, at 12:39, Mathew Savage pcx...@nottingham.ac.uk wrote:
 
 Hi all, first post here.
 
 I am having problems installing fink on my laptop, I have OS X 10.10 with 
 Xcode etc all installed. However when I try to run ./bootstrap.sh I get the 
 following error message;
 
 Mathew-3:fink-0.38.4 pcxms4$ ./bootstrap
 
 Fink must be installed and run with superuser (root) privileges. Fink can
 automatically try to become root when it's run from a user account. Since
 you're currently running this script as a normal user, the method you choose
 will also be used immediately for this script. Available methods:
 
 (1)   Use sudo
 (2)   Use su
 (3)   None, fink must be run as root
 
 Choose a method: [1] 
 
 Checking package... looks good (fink-0.38.4).
 Checking system... i386-apple-darwin14.0.0
 10.90 does not match the expected value of 10.10. Please run `fink 
 selfupdate` to download a newer version of fink at 
 /Users/mathew/Downloads/fink/perlmod/Fink/Services.pm line 1374.
 
 As I don’t yet have Fink installed, I am unable to run fink selfupdate. Are 
 there any known workarounds for this?
 
 Thanks
 
 Mathew

Yeah, that would be an inapplicable message. ;-)

What do you get if you run 

./update/config.guess

from the top level of the fink-0.38.4 directory? Then what do you get when you 
run 

sw_vers

?


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

--
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y___
Fink-users mailing list
Fink-users@lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.macosx.fink.user
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-users


[Fink-users] Failed: phase compiling: libvpx-1.3.0-2 failed

2015-04-28 Thread Luke Coletti

fatal error: too many errors emitted, stopping now [-ferror-limit=]
20 errors generated.
 [CREATE] libs.doxy
 [CC] vpx/src/svc_encodeframe.c.o
 [CC] vpx/src/vpx_decoder.c.o
 [CC] vpx/src/vpx_encoder.c.o
 [CC] vpx/src/vpx_codec.c.o
 [CC] vpx/src/vpx_image.c.o
 [CC] vpx_mem/vpx_mem.c.o
 [CC] vpx_scale/generic/vpx_scale.c.o
 [CC] vpx_scale/generic/yv12config.c.o
 [CC] vpx_scale/generic/yv12extend.c.o
 [CC] vpx_scale/generic/gen_scalers.c.o
 [CC] vpx_scale/vpx_scale_asm_offsets.c.o
 [CC] vpx_scale/vpx_scale_rtcd.c.o
 [CC] vpx_ports/x86_cpuid.c.o
 [CC] vp8/common/alloccommon.c.o
 [CC] vp8/common/blockd.c.o
 [CC] vp8/common/debugmodes.c.o
 [CC] vp8/common/dequantize.c.o
 [CC] vp8/common/entropy.c.o
 [CC] vp8/common/entropymode.c.o
 [CC] vp8/common/entropymv.c.o
 [CC] vp8/common/extend.c.o
 [CC] vp8/common/filter.c.o
 [CC] vp8/common/findnearmv.c.o
 [CC] vp8/common/generic/systemdependent.c.o
 [CC] vp8/common/idct_blk.c.o
 [CC] vp8/common/idctllm.c.o
 [CC] vp8/common/rtcd.c.o
 [CC] vp8/common/loopfilter.c.o
 [CC] vp8/common/loopfilter_filters.c.o
 [CC] vp8/common/mbpitch.c.o
 [CC] vp8/common/modecont.c.o
 [CC] vp8/common/quant_common.c.o
 [CC] vp8/common/reconinter.c.o
 [CC] vp8/common/reconintra.c.o
 [CC] vp8/common/reconintra4x4.c.o
 [CC] vp8/common/sad_c.c.o
 [CC] vp8/common/setupintrarecon.c.o
 [CC] vp8/common/swapyv12buffer.c.o
 [CC] vp8/common/variance_c.c.o
 [CC] vp8/common/treecoder.c.o
 [CC] vp8/common/x86/filter_x86.c.o
 [CC] vp8/common/x86/vp8_asm_stubs.c.o
 [CC] vp8/common/x86/loopfilter_x86.c.o
 [CC] vp8/common/mfqe.c.o
 [CC] vp8/common/postproc.c.o
vp8/common/postproc.c:74:20: warning: unused variable 'kernel5' 
[-Wunused-const-variable]
static const short kernel5[] =
^
 [CC] vp8/common/x86/idct_blk_mmx.c.o
 [CC] vp8/common/x86/variance_mmx.c.o
 [CC] vp8/common/x86/idct_blk_sse2.c.o
 [CC] vp8/common/x86/recon_wrapper_sse2.c.o
 [CC] vp8/common/x86/variance_sse2.c.o
1 warning generated.
 [CC] vp8/common/x86/variance_ssse3.c.o
 [CC] vp8/common/x86/postproc_x86.c.o
 [CC] vp8/vp8_cx_iface.c.o
 [CC] vp8/encoder/bitstream.c.o
 [CC] vp8/encoder/boolhuff.c.o
 [CC] vp8/encoder/dct.c.o
 [CC] vp8/encoder/encodeframe.c.o
 [CC] vp8/encoder/encodeintra.c.o
 [CC] vp8/encoder/encodemb.c.o
 [CC] vp8/encoder/encodemv.c.o
 [CC] vp8/encoder/ethreading.c.o
 [CC] vp8/encoder/firstpass.c.o
 [CC] vp8/encoder/denoising.c.o
 [CC] vp8/encoder/lookahead.c.o
 [CC] vp8/encoder/mcomp.c.o
 [CC] vp8/encoder/modecosts.c.o
 [CC] vp8/encoder/onyx_if.c.o
 [CC] vp8/encoder/pickinter.c.o
 [CC] vp8/encoder/picklpf.c.o
 [CC] vp8/encoder/psnr.c.o
 [CC] vp8/encoder/quantize.c.o
 [CC] vp8/encoder/ratectrl.c.o
vp8/encoder/ratectrl.c:178:18: warning: unused variable 
'kf_boost_seperation_adjustment' [-Wunused-const-variable]
static const int kf_boost_seperation_adjustment[16] =
  ^
 [CC] vp8/encoder/rdopt.c.o
1 warning generated.
 [CC] vp8/encoder/segmentation.c.o
 [CC] vp8/encoder/tokenize.c.o
 [CC] vp8/encoder/treewriter.c.o
 [CC] vp8/encoder/temporal_filter.c.o
 [CC] vp8/encoder/vp8_asm_enc_offsets.c.o
 [CC] vp8/encoder/x86/vp8_enc_stubs_mmx.c.o
 [CC] vp8/encoder/x86/quantize_sse2.c.o
 [CC] vp8/encoder/x86/denoising_sse2.c.o
 [CC] vp8/encoder/x86/vp8_enc_stubs_sse2.c.o
 [CC] vp8/vp8_dx_iface.c.o
 [CC] vp8/decoder/dboolhuff.c.o
 [CC] vp8/decoder/decodemv.c.o
 [CC] vp8/decoder/decodframe.c.o
 [CC] vp8/decoder/detokenize.c.o
 [CC] vp8/decoder/onyxd_if.c.o
 [CC] vp8/decoder/threading.c.o
 [CC] vp9/common/vp9_alloccommon.c.o
 [CC] vp9/common/vp9_convolve.c.o
 [CC] vp9/common/vp9_debugmodes.c.o
 [CC] vp9/common/vp9_entropy.c.o
 [CC] vp9/common/vp9_entropymode.c.o
 [CC] vp9/common/vp9_entropymv.c.o
 [CC] vp9/common/vp9_extend.c.o
 [CC] vp9/common/vp9_filter.c.o
 [CC] vp9/common/vp9_findnearmv.c.o
 [CC] vp9/common/generic/vp9_systemdependent.c.o
 [CC] vp9/common/vp9_idct.c.o
 [CC] vp9/common/vp9_pred_common.c.o
 [CC] vp9/common/vp9_rtcd.c.o
 [CC] vp9/common/vp9_scale.c.o
 [CC] vp9/common/vp9_seg_common.c.o
 [CC] vp9/common/vp9_tile_common.c.o
 [CC] vp9/common/vp9_loopfilter.c.o
 [CC] vp9/common/vp9_loopfilter_filters.c.o
 [CC] vp9/common/vp9_mvref_common.c.o
 [CC] vp9/common/vp9_quant_common.c.o
 [CC] vp9/common/vp9_reconinter.c.o
 [CC] vp9/common/vp9_reconintra.c.o
 [CC] vp9/common/vp9_treecoder.c.o
 [CC] vp9/common/vp9_common_data.c.o
 [CC] vp9/common/vp9_scan.c.o
 [CC] vp9/common/x86/vp9_asm_stubs.c.o
 [CC] vp9/common/x86/vp9_loopfilter_intrin_sse2.c.o
 [CC] vp9/common/x86/vp9_loopfilter_intrin_avx2.c.o
 [CC] 

Re: [Fink-users] Build failure in icon-9.5.0-2 on Yosemite

2015-04-28 Thread Mark D. McKean
On 04/28/2015 09:57 pm, Alexander Hansen wrote:
 The “screw you over” thing was a reference to Homebrew’s use of
 /usr/local.  I’ve been burned by 3rd-party stuff in /usr/local enough
 that it is indeed a sore point.

I guess I don't understand the Darwin implementation well enough. What 
makes /usr/local so potentially problematic? I've installed a number of 
Unix-based packages outside of any package manager--things that have a 
OS X/Darwin-specific installer, such as MacGPG--and they pretty much all 
go into /usr/local.

My current desire to avoid using Homebrew on this system is based more 
on the difficulties I've had keeping track of two separate package 
managers than on any concerns or issues with where it installs. That, 
and I don't care for the lack of local information about their 
packages--you have to visit the project's home page to find out even 
what a package does in some cases.

 Fink used to install in /usr/X11R6 back when X11 was essentially
 impossible to build in alternative trees, but yeah, by policy we try
 to avoid doing anything outside of the Fink tree.  It reduces the
 chance of damaging somebody’s system.

Which makes sense, particularly knowing that you've been burned before.

 It looks like you encountered the second reason we encourage people
 to try building with only one job—some package build systems aren’t
 able to use multiple threads, and this might be one of those.  They
 can be hard to detect because often things will build on the
 maintainer’s machine but not on another with more cpus.

Yeah, I admit I was remiss. Okay, I was lazy and tired. I'll try to 
avoid skipping that step in the future.

 So it looks like icon needs a “UseMaxBuildJobs: false” declaration in
 its .info file.

Another attribute I wouldn't have even guessed existed. I suppose it's 
time for me to dig into more specifics about Fink packaging, huh? 
Especially since I've found two packages I had installed via Homebrew 
before that don't appear to be in Fink yet--they're just games, so it's 
not as though they're really important, but this might be a good 
opportunity for me to learn how to do this. I'd really like to be able 
to help more with this project in general.

Mark D. McKean
qpa...@quantumpanda.com

--
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
___
Fink-users mailing list
Fink-users@lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.macosx.fink.user
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-users


Re: [Fink-users] Build failure in icon-9.5.0-2 on Yosemite

2015-04-28 Thread Matthias Neeracher
 The “screw you over” thing was a reference to Homebrew’s use of /usr/local.  
 I’ve been burned by 3rd-party stuff in /usr/local enough that it is indeed a 
 sore point. 
 
 Fink used to install in /usr/X11R6 back when X11 was essentially impossible 
 to build in alternative trees, but yeah, by policy we try to avoid doing 
 anything outside of the Fink tree.  It reduces the chance of damaging 
 somebody’s system.
 
 It looks like you encountered the second reason we encourage people to try 
 building with only one job—some package build systems aren’t able to use 
 multiple threads, and this might be one of those.  They can be hard to detect 
 because often things will build on the maintainer’s machine but not on 
 another with more cpus.  
 
 So it looks like icon needs a “UseMaxBuildJobs: false” declaration in its 
 .info file.

I just committed an update of the icon package to 9.5.1 which should be fixing 
all the outstanding issues. Thanks for the report.

Matthias

--
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y___
Fink-users mailing list
Fink-users@lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.macosx.fink.user
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-users


Re: [Fink-users] Build failure in icon-9.5.0-2 on Yosemite

2015-04-28 Thread Alexander Hansen

 On Apr 28, 2015, at 19:46, Mark D. McKean qpa...@quantumpanda.com wrote:
 
 On 04/28/2015 09:57 pm, Alexander Hansen wrote:
 The “screw you over” thing was a reference to Homebrew’s use of
 /usr/local.  I’ve been burned by 3rd-party stuff in /usr/local enough
 that it is indeed a sore point.
 
 I guess I don't understand the Darwin implementation well enough. What 
 makes /usr/local so potentially problematic? I've installed a number of 
 Unix-based packages outside of any package manager--things that have a 
 OS X/Darwin-specific installer, such as MacGPG--and they pretty much all 
 go into /usr/local.
 
 My current desire to avoid using Homebrew on this system is based more 
 on the difficulties I've had keeping track of two separate package 
 managers than on any concerns or issues with where it installs. That, 
 and I don't care for the lack of local information about their 
 packages--you have to visit the project's home page to find out even 
 what a package does in some cases.
 
 Fink used to install in /usr/X11R6 back when X11 was essentially
 impossible to build in alternative trees, but yeah, by policy we try
 to avoid doing anything outside of the Fink tree.  It reduces the
 chance of damaging somebody’s system.
 
 Which makes sense, particularly knowing that you've been burned before.
 
 It looks like you encountered the second reason we encourage people
 to try building with only one job—some package build systems aren’t
 able to use multiple threads, and this might be one of those.  They
 can be hard to detect because often things will build on the
 maintainer’s machine but not on another with more cpus.
 
 Yeah, I admit I was remiss. Okay, I was lazy and tired. I'll try to 
 avoid skipping that step in the future.
 
 So it looks like icon needs a “UseMaxBuildJobs: false” declaration in
 its .info file.
 
 Another attribute I wouldn't have even guessed existed. I suppose it's 
 time for me to dig into more specifics about Fink packaging, huh? 
 Especially since I've found two packages I had installed via Homebrew 
 before that don't appear to be in Fink yet--they're just games, so it's 
 not as though they're really important, but this might be a good 
 opportunity for me to learn how to do this. I'd really like to be able 
 to help more with this project in general.
 
 Mark D. McKean
 qpa...@quantumpanda.com
 
 -

The big deal with /usr/local is that it’s pretty darn hard to hide from the 
build tools, so that headers and libraries that live there tend to get picked 
up automatically.  That can be a problem for Fink builds because (1) they 
aren’t necessarily compatible, and (2) by removing them the relevant Fink 
package will be broken.



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


--
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
___
Fink-users mailing list
Fink-users@lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.macosx.fink.user
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-users


[Fink-users] Installation problems

2015-04-28 Thread Mathew Savage
Hi all, first post here.

I am having problems installing fink on my laptop, I have OS X 10.10 with Xcode 
etc all installed. However when I try to run ./bootstrap.sh I get the following 
error message;

Mathew-3:fink-0.38.4 pcxms4$ ./bootstrap

Fink must be installed and run with superuser (root) privileges. Fink can
automatically try to become root when it's run from a user account. Since
you're currently running this script as a normal user, the method you choose
will also be used immediately for this script. Available methods:

(1) Use sudo
(2) Use su
(3) None, fink must be run as root

Choose a method: [1]

Checking package... looks good (fink-0.38.4).
Checking system... i386-apple-darwin14.0.0
10.90 does not match the expected value of 10.10. Please run `fink selfupdate` 
to download a newer version of fink at 
/Users/mathew/Downloads/fink/perlmod/Fink/Services.pm line 1374.

As I don’t yet have Fink installed, I am unable to run fink selfupdate. Are 
there any known workarounds for this?

Thanks

Mathew




This message and any attachment are intended solely for the addressee
and may contain confidential information. If you have received this
message in error, please send it back to me, and immediately delete it. 

Please do not use, copy or disclose the information contained in this
message or in any attachment.  Any views or opinions expressed by the
author of this email do not necessarily reflect the views of the
University of Nottingham.

This message has been checked for viruses but the contents of an
attachment may still contain software viruses which could damage your
computer system, you are advised to perform your own checks. Email
communications with the University of Nottingham may be monitored as
permitted by UK legislation.

--
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y___
Fink-users mailing list
Fink-users@lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.macosx.fink.user
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-users