From: Nikos Chantziaras <realnc@arcor.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: In search for a undeclared identifier...
Date: Mon, 17 Aug 2009 08:01:48 +0300 [thread overview]
Message-ID: <h6ao7q$qep$1@ger.gmane.org> (raw)
In-Reply-To: <20090817105259.1ad60968@malediction>
On 08/17/2009 07:52 AM, Mike Kazantsev wrote:
> On Mon, 17 Aug 2009 09:42:12 +0600
> Mike Kazantsev<mk.fraggod@gmail.com> wrote:
>
>> On Mon, 17 Aug 2009 05:20:05 +0200
>> meino.cramer@gmx.de wrote:
>>
>>> I try to build the developper branch of a software project,
>>> which is not in Gentoo.
>>>
>>> This works a longer time.
>>>
>>> Now the compilatino process aborts with
>>>
>>> glmodule.c:926: error: 'glActiveTexture' undeclared (first use in
>>> this function) .
>>>[...]
>>
>> On my system it's in /usr/include/GL/glew.h header, which belongs to
>> media-libs/glew, so you probably need to have it installed.
>
> My bad, I've misread grep results. It really is
> in /usr/include/GL/glext.h.
> And that file should be symlink created by "eselect opengl" with
> source belonging either to media-libs/mesa or nvidia drivers.
>
> If source file include lines are correct, you might want to try
> re-emerging nvidia drivers and eselect'ing them.
The header file is probably installed correctly, since the compiler's
error complains about an undeclared identifier rather than a
non-existent header ("error: GL/glext.h: No such file or directory").
next prev parent reply other threads:[~2009-08-17 5:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-17 3:20 [gentoo-user] In search for a undeclared identifier meino.cramer
2009-08-17 3:42 ` Mike Kazantsev
2009-08-17 4:52 ` Mike Kazantsev
2009-08-17 5:01 ` Nikos Chantziaras [this message]
2009-08-17 15:51 ` meino.cramer
2009-08-17 16:09 ` [gentoo-user] " Nikos Chantziaras
2009-08-17 16:23 ` meino.cramer
2009-08-17 4:07 ` Nikos Chantziaras
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='h6ao7q$qep$1@ger.gmane.org' \
--to=realnc@arcor.de \
--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