Re: [gentoo-user] Re: how to track this down (emerge of amaya)
Hi, On Fri, 10 Mar 2006 12:01:04 -0600 Harry Putnam [EMAIL PROTECTED] 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
[gentoo-user] Re: how to track this down (emerge of amaya)
Hans-Werner Hilse [EMAIL PROTECTED] 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 [EMAIL PROTECTED] 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