> On May 23, 2017, at 13:43, Paul, Don <d.m.p...@warwick.ac.uk> wrote:
> 
> Been away for a while, now having problems installing fink on my new laptop. 
> Anyone see what I’ve done wrong, I’m sure its a silly problem but living in a 
> pc world for a while gives you funny ideas?
> 
> Don
> 
> 
<make plain text and snip>

> c++ -c -MD -DHAVE_CONFIG_H -D_REENTRANT 
> -I/sw/src/fink.build/apt-0.5.4-1061/apt-0.5.4/include -O2 -DEMULATE_MMAP 
> -D__USE_MISC -fconstant-cfstrings -DHAVE_SOCKLEN_T=1 -O2 -DEMULATE_MMAP 
> -D__USE_MISC -fconstant-cfstrings -DHAVE_SOCKLEN_T=1 -O2 -DEMULATE_MMAP 
> -D__USE_MISC -fconstant-cfstrings -DHAVE_SOCKLEN_T=1 -fno-common -DPIC -o 
> /sw/src/fink.build/apt-0.5.4-1061/apt-0.5.4/obj/apt-inst/debfile.opic 
> deb/debfile.cc
> dirstream.cc:18:10: fatal error: 'apt-pkg/dirstream.h' file not found
> #include <apt-pkg/dirstream.h>
>          ^
> 1 error generated.
> make[2]: *** 
> [/sw/src/fink.build/apt-0.5.4-1061/apt-0.5.4/obj/apt-inst/dirstream.opic] 
> Error 1
> make[2]: *** Waiting for unfinished jobs….

The above was the error. 

> 

> Also include the following system information:
> Package manager version: 0.41.1
> Distribution version: selfupdate-point (bootstrap), 10.12, x86_64
> Trees: local/main stable/main
> Xcode.app: 8.3.2
> Xcode command-line tools: 8.3.2.0.1.1492020469
> Max. Fink build jobs:  8
> 
> 
> ERROR: Bootstrap phase 2 failed!

Unfortunately, one side effect of multiple build jobs is that the console 
output doesn’t stay synchronized to any particular thread, and that can make 
error messages appear a long way away from from what actually triggered them.  

I didn’t reproduce this here with 10.12.5/Xcode Tools 8.3.2/4 jobs, so my 
initial guess is that some third-party tool might be 

Try the following:

1) Go ahead and manually run the following commands.  apt is the last package 
built, and it’s not actually mandatory for source operations, so your install 
should actually have base functionality.

$ /sw/bin/pathsetup.sh
$ fink --no-use-binary-dist selfupdate

(then select your preferred selfupdate method)

2)  Run “fink configure” and set your build jobs to 1 when it asks about that:

Enter the maximum number of simultaneous build jobs. In general, Fink will
build packages faster on systems with multiple CPUs/cores if you allow it to
spawn jobs in parallel. You have 4 active CPUs/cores on your system.
Maximum number of simultaneous build jobs: [8] *1*

3)  Try “fink -l build apt”.  With a single build job the output should be 
easier to parse.  Look for "dirstream.cc:18:10: fatal error: 
'apt-pkg/dirstream.h' file not found" again, and post a few complete output 
lines on either side of that.

This will also capture a log file in /private/tmp.  I’d recommend moving that 
to your home directory so that it won’t get lost after a reboot, just in case 
we need to delve into things more deeply.  But don’t send it to the mailing 
list, please, unless we ask for some portion of it.

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


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Fink-users mailing list
Fink-users@lists.sourceforge.net
List archive:
https://sourceforge.net/p/fink/mailman/fink-users/
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-users

Reply via email to