Re: TiBook w/-current semi-comatose building boost-libs

[email protected] (Christos Zoulas)
Newsgroups gmane.os.netbsd.ports.macppc
Message-ID <[email protected]>
In article <[email protected]>,
John D. Baker <[email protected]> wrote:
>On Mon, 5 Oct 2020, John D. Baker wrote:
>
>> On Mon, 5 Oct 2020, David Brownlee wrote:
>> 
>> > On Mon, 5 Oct 2020 at 13:30, John D. Baker <[email protected]> wrote:
>> > >
>> > > Except, when it tries to build "devel/boost-libs".  It gets as far as:
>> > >
>> > > Ideas?
>> > 
>> > Some random thoughts:
>> > - Can you see if there is any interesting (nfs) traffic?
>> > - Does ^T give any output (or ^C)
>> 
>> I'll see about gathering this when I next attempt to build
>> "devel/boost-libs".  Right now, I have it and everything that depends
>> on it eXcluded via 'pkg_rolling-replace -u -Xfoo,bar,baz,qux' and
>> pkg_rr is rolling right along.
>
>I've had it come to a similar impasse while building "qt5-qtbase".
>While it echoed <space><backspace> in the SSH session and the login
>on the console accepted characters, it was unresponsive to ^T or ^C.
>
>It got as far as:
>
>[...]
>=> Generating pkg-config file for builtin expat package.
>=> Replacing Perl interpreter in bin/fixqt4headers.pl bin/syncqt.pl
>mkspecs/features/data/unix/findclasslist.pl.
>Creating qmake...
>..............[stuck]
>
>> > - Does it have plenty of swap configured
>> 
>> It has 2GB in "/swap" (1GB RAM).  I'll see about increasing this.
>> 
>> > - How reproducible is it (maybe leave a separate ssh session running
>> > top & unblanked console)
>> 
>> I'll see if I can arrange the extra session or run 'top' on console but so
>> far it is completely reproducible, any attempt to build "devel/boost-libs"
>> hangs as described previously.
>
>A second ssh session running 'top' is now frozen displaying the following:

Try updating to HEAD. There have been quite a few MI fixes thanks to chuq.

christos
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.