public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jeremy McSpadden <deface@uberpenguin.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] xscreensaver compilation failed
Date: Mon, 03 Nov 2008 02:21:44 -0600	[thread overview]
Message-ID: <1225700504.28287.5.camel@localhost> (raw)
In-Reply-To: <de2610f90811030017oae699aar8e8e31d5234f32ff@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2303 bytes --]

On Mon, 2008-11-03 at 16:17 +0800, Ducky wrote:

> I'm sorry. I've now attached the build.log.
> 
> 
> 
> On Mon, Nov 3, 2008 at 4:10 PM, Jeremy McSpadden <deface@uberpenguin.net> wrote:
> > On Mon, 2008-11-03 at 16:01 +0800, Ducky wrote:
> >
> > Hello,
> >
> > My xscreensaver failed to build. Not sure what's wrong. I've tried
> > versions starting from 5.05.
> >
> > [ebuild  N    ] x11-misc/xscreensaver-5.07  USE="jpeg opengl pam suid
> > xinerama -new-login" 0 kB
> >
> > I tried to disable each options, it didn't help much.
> >
> > It failed at econf.
> >
> > ...
> > config.status: creating driver/XScreenSaver.ad
> > config.status: creating config.h
> > config.status: executing default-1 commands
> > config.status: executing po/stamp-it commands
> > config.status: error: po/Makefile.in.in was not created by intltoolize.
> > ...
> > ...
> >  *
> >  * ERROR: x11-misc/xscreensaver-5.07 failed.
> >  * Call stack:
> >  * ebuild.sh, line   49:  Called src_compile
> >  * environment, line 2950:  Called econf
> > '--with-x-app-defaults=/usr/share/X11/app-defaults'
> > '--with-hackdir=/usr/lib/misc/xscreensaver'
> > '--with-configdir=/usr/share/xscreensaver/config'
> > '--x-libraries=/usr/lib' '--x-includes=/usr/include' '--with-dpms-ext'
> > '--with-xf86vmode-ext' '--with-xf86gamma-ext' '--with-randr-ext'
> > '--with-proc-interrupts' '--with-xpm' '--with-xshm-ext'
> > '--with-xdbe-ext' '--enable-locking' '--without-kerberos'
> > '--without-gle' '--with-gtk' '--with-pixbuf' '--with-setuid-hacks'
> > '--without-login-manager' '--with-xinerama-ext' '--with-pam'
> > '--without-gl' '--with-jpeg'
> >  * ebuild.sh, line  525:  Called die
> >  * The specific snippet of code:
> >  * die "econf failed"
> >  * The die message:
> >  * econf failed
> >  *
> >  * If you need support, post the topmost build error, and the call
> > stack if relevant.
> >  * A complete build log is located at
> > '/var/tmp/portage/x11-misc/xscreensaver-5.07/temp/build.log'.
> >  * The ebuild environment file is located at
> > '/var/tmp/portage/x11-misc/xscreensaver-5.07/temp/environment'.
> >  *
> >
> > Any idea?
> >
> > Thanks,
> >
> > I'd try posting the full log, not the snippets you think are relevant.
> >
> >
> >
> 
> 
> 

That looks like an env, not a build log.

Jeremy McSpadden
UberPenguin.net

[-- Attachment #2: Type: text/html, Size: 2789 bytes --]

  parent reply	other threads:[~2008-11-03  8:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-03  8:01 [gentoo-user] xscreensaver compilation failed Ducky
2008-11-03  8:10 ` Jeremy McSpadden
2008-11-03  8:17   ` Ducky
2008-11-03  8:17     ` Ducky
2008-11-03  8:22       ` Ducky
2008-11-03  8:21     ` Jeremy McSpadden [this message]
2008-11-03  8:35       ` Ducky
2008-11-03  8:40         ` Jeremy McSpadden
2008-11-03  8:54           ` Ducky

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1225700504.28287.5.camel@localhost \
    --to=deface@uberpenguin.net \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox