From: JinzhongLin <lithlin@gmail.com>
To: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] problem in coot-0.3.1 ebuild
Date: Mon, 25 Jun 2007 16:10:29 +0800 [thread overview]
Message-ID: <1182759029.8056.4.camel@localhost> (raw)
In-Reply-To: <467F6A19.5060904@gentoo.org>
在 2007-06-25一的 00:09 -0700，Donnie Berkholz写道：
> JinzhongLin wrote:
> > when i install coot-0.3.1, the configuratin was stuck reporting GLUT
> > missing, although GLUT did exist in the system. In the ebuild there is a
> > variable with(out)-gtk2 passed into the configuration, i don't know what
> > it is. but Deleteing it solved the glut problem. why it that??
>
> Are you building without USE="new-interface"? If so, try with. It could
> be that the configure script is broken when passing --without-gtk2.
>
> Thanks,
> Donnie
>
i got the same problem with USE="new-interface" and moreover it seems
like coot-0.3.1 couldn't be compiled aganist guile-gtk-2*
--
gentoo-science@gentoo.org mailing list
next prev parent reply other threads:[~2007-06-25 8:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-25 6:39 [gentoo-science] problem in coot-0.3.1 ebuild JinzhongLin
2007-06-25 7:09 ` Donnie Berkholz
2007-06-25 8:10 ` JinzhongLin [this message]
2007-06-25 18:21 ` Donnie Berkholz
2007-06-26 6:08 ` JinzhongLin
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=1182759029.8056.4.camel@localhost \
--to=lithlin@gmail.com \
--cc=gentoo-science@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