kde3 Make Install failure
Brooks Davis
brooks at one-eyed-alien.net
Tue Aug 22 18:21:25 UTC 2006
On Tue, Aug 22, 2006 at 10:36:30AM -0700, Vizion wrote:
> > -----Original Message-----
> > From: Brooks Davis [mailto:brooks at one-eyed-alien.net]
> > Sent: Tuesday, August 22, 2006 10:20 AM
> > To: Vizion
> > Cc: freebsd-questions at freebsd.org; amd64 at freebsd.org
> > Subject: Re: kde3 Make Install failure
> >
> >
> > On Tue, Aug 22, 2006 at 10:00:35AM -0700, Vizion wrote:
> > > Trying to compile and install kde3
> > > on amd64 FreeBSD 6.1-RELEASE #0. kde3 fails a test and then hangs.
> > >
> > > cd /usr/ports/x11/kde3
> > >
> > > Make runs fine but then:
> > >
> > > # Make Install
> > >
> > > terminates and hangs with following consol message:
> > >
> > --------------------------------------------------------------
> > -----------
> > >
> > > set listen [lindex [fconfigure $s -sockname] 2]
> > > set s1 [socket [info hostname] $listen]
> > > set timer [aftyer 10000 "set x timed_out"]
> > > vwait x
> > > after cancel $timer
> > > close $s
> > > close $s1
> > > set 1 ""
> > > lappend l [expr {[lindex $x 2] -- $listen}] [llength $x]
> > >
> > > ---- Test generated error; return code was:1
> > > ---- Return code should have been one of: 0 2
> > > ---- errorInfo: couldn't open socket: connection timed out
> > > wgile executing
> > > "socket {info hostname] $listen]"
> > > invoked from within
> > > "set s1 [socket [info gostname] $listen]"
> > > ("uplevel" body line 9)
> > > invoked from within
> > > "uplevel 1 $script"
> > > ---- errorCode: PSIX ERIMWOUT {connection timed out}
> > > ==== socket-7.4 FAILED
> > >
> > > -------------------------------------------------------------------
> > >
> > >
> > > Does anyone gave any idea what may be happening here??
> >
> > One of the ports kde3 has a RUN_DEPEND on failed to build.
> > There isn't
> > enough information here to know more. Running "make" in x11/kde3 is a
> > no-op since the port just maintains dependancies to other kde bundles.
> >
> > -- Brooks
>
> Thanks for yr help.
>
> How do I get the information necessary to solve this?
You've trimmed the output at the end which included the name
of the port that failed. Once you know that you can make sure it's up
to date and then contact the maintainer of that port for debugging
assistance.
-- Brooks
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-amd64/attachments/20060822/788c5e15/attachment.pgp
More information about the freebsd-amd64
mailing list