samba3: autoconf never completes/stops

[xanda-escuyer (xanda)]

samba3 install never progresses beyond autoconf.

Installation command:-

port -t -N install samba3 +universal

Terminal output (partial):-

--->  Fetching archive for samba3
--->  Attempting to fetch samba3-3.6.25_4+universal.darwin_9.i386-ppc.tbz2 from http://packages.macports.org/samba3
--->  Attempting to fetch samba3-3.6.25_4+universal.darwin_9.i386-ppc.tbz2 from http://mse.uk.packages.macports.org/samba3
--->  Attempting to fetch samba3-3.6.25_4+universal.darwin_9.i386-ppc.tbz2 from http://fra.de.packages.macports.org/samba3
--->  Fetching distfiles for samba3
--->  Verifying checksums for samba3
--->  Extracting samba3
--->  Applying patches to samba3
--->  Configuring samba3
      [   •   •   •   •   •   •   •   •   •   •   •   •]

It's been on this stage for about 4 days now and shows no sign of change. Included is a copy of config.log and the open files & handles as reported by activity manager (which also has not changed)

[xanda-escuyer (xanda)]

Open files and handles as reported by Activity Manager

[xanda-escuyer (xanda)]

config.log as generated by/for autoconf

[ryandesign (Ryan Carsten Schmidt)]

On my 2016 2.7GHz MacBook Pro with Catalina samba3 takes 109 seconds to extract and configure without trace mode or 149 seconds with trace mode. I see you're on Leopard and building universal for ppc and i386 so you'll be on a slower computer, probably many times slower, so it should take longer. But four days does seem unlikely to be correct.

If you like you can cancel the configuration and try again, adding the -d port flag to display debug output (sudo port -dtN install samba3 +universal). That way you can see exactly what it's doing as it does it and you can notice if any particular step seems to slow down or stop.

[jmroot (Joshua Root)]

Leopard is known to have some odd issues like #62994. Not sure if that's related to what's happening here.

[xanda-escuyer (xanda)]

Thanks very much for the feedback. Our platform is a 1.4PPC/G4 and yes, builds can take a fair amount of time (for example gcc has taken just as long before now).

Attached are additional logs produced with -d flag; please help us understand what they reveal.

Thanks.

[xanda-escuyer (xanda)]

conftest log with -d flag

[xanda-escuyer (xanda)]

Screen output using -d flag

[xanda-escuyer (xanda)]

Screen output post ^C/SIGINT