[gentoo-user] how to track this down (emerge of amaya)

[gentoo-user] how to track this down (emerge of amaya)

[Harry Putnam]

Attempting to emerge www-client/amaya
The tail end of emerge shows:

i686-pc-linux-gnu-g++: ../redland/raptor/.libs/libraptor.a: No such file or directory
make[1]: *** [../bin/amaya] Error 1
make[1]: Leaving directory `/var/tmp/portage/amaya-8.7/work/Amaya/LINUX-ELF/amaya'
make: *** [amaya_prog] Error 2

!!! ERROR: www-client/amaya-8.7 failed.

media-libs/raptor is installed.

How to track this down?

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] how to track this down (emerge of amaya)

[Hans-Werner Hilse]

Hi,

On Thu, 09 Mar 2006 17:49:28 -0600 Harry Putnam <reader@newsguy.com>
wrote:

> Attempting to emerge www-client/amaya
> The tail end of emerge shows:
> 
> i686-pc-linux-gnu-g++: ../redland/raptor/.libs/libraptor.a: No such
> file or directory make[1]: *** [../bin/amaya] Error 1
> make[1]: Leaving directory
> `/var/tmp/portage/amaya-8.7/work/Amaya/LINUX-ELF/amaya' make: ***
> [amaya_prog] Error 2
> 
> !!! ERROR: www-client/amaya-8.7 failed.
> 
> media-libs/raptor is installed.
> 
> How to track this down?

The ebuild needs a fix, or even better: upstream needs to be fixed.
It's mentioned in bugzilla already (gentoo bugzilla, that is).

I helped myself by compiling manually. The same problem occurs, but you
can simply change the directory to Amaya/WX/redland/raptor, type
"make", return to "Amaya/WX/amaya" and continue building with another
"make". This would also give you a more current version of amaya, the
one in portage is a little bit older.

-hwh
-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: how to track this down (emerge of amaya)

[Harry Putnam]

Hans-Werner Hilse <hilse@web.de> writes:

> The ebuild needs a fix, or even better: upstream needs to be fixed.
> It's mentioned in bugzilla already (gentoo bugzilla, that is).
>
> I helped myself by compiling manually. The same problem occurs, but you
> can simply change the directory to Amaya/WX/redland/raptor, type
> "make", return to "Amaya/WX/amaya" and continue building with another
> "make". This would also give you a more current version of amaya, the
> one in portage is a little bit older.

Thanks... I noticed the portage version was bit aged.  And in fact I
downloaded the current version and was going to try to build it but
thought by installing the portage version first I'd sort of gaurantee
the libs needed would be on board.

Thanks for the tip about chdir and make...

-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: how to track this down (emerge of amaya)

[Harry Putnam]

Harry Putnam <reader@newsguy.com> writes:

>> I helped myself by compiling manually. The same problem occurs, but you
>> can simply change the directory to Amaya/WX/redland/raptor, type
>> "make", return to "Amaya/WX/amaya" and continue building with another
>> "make". This would also give you a more current version of amaya, the
>> one in portage is a little bit older.
>
> Thanks... I noticed the portage version was bit aged.  And in fact I
> downloaded the current version and was going to try to build it but
> thought by installing the portage version first I'd sort of gaurantee
> the libs needed would be on board.
>
> Thanks for the tip about chdir and make...

What did you do about Mesa? Just leave it out.  I see the Mesa libs
are masked even though I'm running ~x86 enabled in /etc/make.conf

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: how to track this down (emerge of amaya)

[Hans-Werner Hilse]

Hi,

On Fri, 10 Mar 2006 12:01:04 -0600
Harry Putnam <reader@newsguy.com> wrote:

> What did you do about Mesa? Just leave it out.  I see the Mesa libs
> are masked even though I'm running ~x86 enabled in /etc/make.conf

Oooh, yeah, i actually left out that part. First, I emerged "wxGTK" with
opengl USE-flag set (among "X" and "unicode").

I think compiling amaya went fine then until the final linking run. It
even compiled wxGTK and I had some strong feeling that there was an
error. I "fixed" the gcc linking run by removing references to the
amaya-wxGTK and substituted dynamic linking to the wxGTK installed via
portage. Too bad I didn't remember to turn screen's logging on when I
did that...

-hwh
-- 
gentoo-user@gentoo.org mailing list