[gentoo-user] espxe masked by missing keyword

[gentoo-user] espxe masked by missing keyword

[Andrew Syrewicze]

I've been trying to emerge epsxe but it is masked by a missing keyword?
how do i go about unmasking this package???  I'm new to gentoo and portage.

thanks all

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

Re: [gentoo-user] espxe masked by missing keyword

[Daniel Iliev]

Andrew Syrewicze wrote:
> I've been trying to emerge epsxe but it is masked by a missing keyword?
> how do i go about unmasking this package???  I'm new to gentoo and portage.
>
> thanks all
>
>     -ando
>   
Have you synced your portage tree recently with "emerge --sync" ?
My system lets me install this package:

me@localhost ~ $ emerge -p epsxe

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild  N    ] games-emulation/psemu-gpupetemesagl-1.76
[ebuild  N    ] games-emulation/psemu-peopsspu-1.0.9  USE="alsa oss"
[ebuild  N    ] games-emulation/epsxe-1.6.0-r3  USE="opengl"
me@localhost ~ $

-- 
Best regards,
Daniel


-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] espxe masked by missing keyword

[Andrew Syrewicze]

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

Daniel Iliev wrote:
> Andrew Syrewicze wrote:
>   
>> I've been trying to emerge epsxe but it is masked by a missing keyword?
>> how do i go about unmasking this package???  I'm new to gentoo and portage.
>>
>> thanks all
>>
>>     -ando
>>   
>>     
> Have you synced your portage tree recently with "emerge --sync" ?
> My system lets me install this package:
>
> me@localhost ~ $ emerge -p epsxe
>
> These are the packages that would be merged, in order:
>
> Calculating dependencies... done!
> [ebuild  N    ] games-emulation/psemu-gpupetemesagl-1.76
> [ebuild  N    ] games-emulation/psemu-peopsspu-1.0.9  USE="alsa oss"
> [ebuild  N    ] games-emulation/epsxe-1.6.0-r3  USE="opengl"
> me@localhost ~ $
>
>   
Yeah I synced it before I tried emerging the package. I'm useing the
amd64 distro btw. Forgot to mention that.

Is it maybe just a problem with the 64bit distro???

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

Re: [gentoo-user] espxe masked by missing keyword

[Jesús Guerrero]

El Miércoles, 9 de Agosto de 2006 08:59, Andrew Syrewicze escribió:
> Daniel Iliev wrote:
> > Andrew Syrewicze wrote:
> >> I've been trying to emerge epsxe but it is masked by a missing keyword?
> >> how do i go about unmasking this package???  I'm new to gentoo and
> >> portage.
> >>
> >> thanks all
> >>
> >>     -ando
> >
> > Have you synced your portage tree recently with "emerge --sync" ?
> > My system lets me install this package:
> >
> > me@localhost ~ $ emerge -p epsxe
> >
> > These are the packages that would be merged, in order:
> >
> > Calculating dependencies... done!
> > [ebuild  N    ] games-emulation/psemu-gpupetemesagl-1.76
> > [ebuild  N    ] games-emulation/psemu-peopsspu-1.0.9  USE="alsa oss"
> > [ebuild  N    ] games-emulation/epsxe-1.6.0-r3  USE="opengl"
> > me@localhost ~ $
>
> Yeah I synced it before I tried emerging the package. I'm useing the
> amd64 distro btw. Forgot to mention that.
>
> Is it maybe just a problem with the 64bit distro???

Yes, epsxe, zsnes, and most emulators, have parts in assembler that will not 
compile or work as expected in any other arch than the one that they were 
made for. Epsxe is not keyworded for amd64, I suppose, cause it would not 
work in such architecture.

I dont have any accurate info about it, but if it is masked in amd64 is for a 
reason. You can always try to add the ~amd64 keyword to the ebuild and the 
emerge it, at your own risk, of course.

Jesús.

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] espxe masked by missing keyword

[Friedrich Göpel]

On 8/9/06, Jesús Guerrero <6thpink@terra.es> wrote:
> Yes, epsxe, zsnes, and most emulators, have parts in assembler that will not
> compile or work as expected in any other arch than the one that they were
> made for. Epsxe is not keyworded for amd64, I suppose, cause it would not
> work in such architecture.
>
Nope, not true.
Not even for ZSNES.
What you said is true if you are trying to compile 32 bit assembler
code in a 64 bit binary (or linking a 64 bit lib in a 32 bit binary -
or vice versa), but if you just compile it 32 bit, which x86_64 gcc
supports  out of the box there is no problem.
Plus, you are aware that amd64 is 32 bit compatible?
You just can't mix *in one program*, that's all.
Additionally, since epsxe is not open source, there is nothing to
compile, it's just unpacking the tarball and having 32 bit gtk-1 libs
installed, that's it.
> I dont have any accurate info about it, but if it is masked in amd64 is for a
> reason. You can always try to add the ~amd64 keyword to the ebuild and the
> emerge it, at your own risk, of course.
>
The reason seems to be the existence of non-binary plugins for epsxe,
where the ebuilds don't check for amd64 and set the ABI to 32 bit,
plus pull in the necessary emul-linux-x86 libs.
Apart from that 32 bit binaries on amd64 are 100% normal and supported.

> Jesús.
>

Cheers,

Friedrich Göpel

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] espxe masked by missing keyword

[Jesús Guerrero]

El Miércoles, 9 de Agosto de 2006 19:02, Friedrich Göpel escribió:
> On 8/9/06, Jesús Guerrero <6thpink@terra.es> wrote:
> > Yes, epsxe, zsnes, and most emulators, have parts in assembler that will
> > not compile or work as expected in any other arch than the one that they
> > were made for. Epsxe is not keyworded for amd64, I suppose, cause it
> > would not work in such architecture.
>
> Nope, not true.
> Not even for ZSNES.
> What you said is true if you are trying to compile 32 bit assembler
> code in a 64 bit binary (or linking a 64 bit lib in a 32 bit binary -
> or vice versa), but if you just compile it 32 bit, which x86_64 gcc
> supports  out of the box there is no problem.

> Plus, you are aware that amd64 is 32 bit compatible?
> You just can't mix *in one program*, that's all.
> Additionally, since epsxe is not open source, there is nothing to
> compile, it's just unpacking the tarball and having 32 bit gtk-1 libs
> installed, that's it.
>
I know that amd64 supports the x86 32 bits code out of the box. And, as I 
said, what I was talking about epsxe was all about assuptions, since I do not 
know anything about epsxe at all (still the error was mine, for talking 
without having all the info and about an assumption :P ). I just supposed it 
was the same case than in zsnes.

And it is true that zsnes will not compile in amd64 out of the box at all. The 
reasons are well explained in the zsnes forums. And since I dont have enough 
knowledge about the amd64 asm nor the zsnes code I will not try to explain 
here. The devs there have far more idea than me about the issue. A native 
amd64 version is in the way, though. It seems to be not a big problem to get 
it working natively under amd64. But some changes are required to compile the 
assembler in 64bits instead of 32 and use emul libs.

> > I dont have any accurate info about it, but if it is masked in amd64 is
> > for a reason. You can always try to add the ~amd64 keyword to the ebuild
> > and the emerge it, at your own risk, of course.
>
> The reason seems to be the existence of non-binary plugins for epsxe,
> where the ebuilds don't check for amd64 and set the ABI to 32 bit,
> plus pull in the necessary emul-linux-x86 libs.
> Apart from that 32 bit binaries on amd64 are 100% normal and supported.

That is true. I did not know that epsxe was a binary only package. Then the 
problems should be easily solved by just using the correct emul libs and 
compiling the plugins by hand -in those cases where a bin version is not 
available.

Regards, people.

Jesús.

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] espxe masked by missing keyword

[Neil Bothwick]

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

On Tue, 08 Aug 2006 19:57:18 +0000, Andrew Syrewicze wrote:

> I've been trying to emerge epsxe but it is masked by a missing keyword?
> how do i go about unmasking this package???  I'm new to gentoo and
> portage.

When you receive an error message, please post the exact message with
some context. The more precise your question, the more precise the
answers you will receive.


-- 
Neil Bothwick

Top Oxymorons Number 19: Passive aggression

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] espxe masked by missing keyword

[Andrew Syrewicze]

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

Neil Bothwick wrote:
> On Tue, 08 Aug 2006 19:57:18 +0000, Andrew Syrewicze wrote:
>
>   
>> I've been trying to emerge epsxe but it is masked by a missing keyword?
>> how do i go about unmasking this package???  I'm new to gentoo and
>> portage.
>>     
>
> When you receive an error message, please post the exact message with
> some context. The more precise your question, the more precise the
> answers you will receive.
>
>
>   
here is the output from portage when I try to emerge


DreamMachine asyrewicze # emerge --ask epsxe

These are the packages that would be merged, in order:

Calculating dependencies
!!! All ebuilds that could satisfy "epsxe" have been masked.
!!! One of the following masked packages is required to complete your
request:
- games-emulation/epsxe-1.6.0-r3 (masked by: missing keyword)
- games-emulation/epsxe-1.5.2-r1 (masked by: missing keyword)

For more information, see MASKED PACKAGES section in the emerge man page or
refer to the Gentoo Handbook.


I don't know how to go about unmasking an unknown keyword. Any Ideas anyone

-A



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

Re: [gentoo-user] espxe masked by missing keyword

[Neil Bothwick]

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

On Wed, 09 Aug 2006 06:54:41 +0000, Andrew Syrewicze wrote:

> Calculating dependencies
> !!! All ebuilds that could satisfy "epsxe" have been masked.
> !!! One of the following masked packages is required to complete your
> request:
> - games-emulation/epsxe-1.6.0-r3 (masked by: missing keyword)
> - games-emulation/epsxe-1.5.2-r1 (masked by: missing keyword)
> 
> For more information, see MASKED PACKAGES section in the emerge man
> page or refer to the Gentoo Handbook.
> 
> 
> I don't know how to go about unmasking an unknown keyword. Any Ideas
> anyone

See the documentation mentioned above. In this case, both the ebuilds
contain KEYWORDS="-* x86". this means they only run on x86 (the -*
explicitly excludes everything else). You mentioned in your other post
that you are using amd64, it appear this package will not run on amd64.

If it was simply a case of not being tested on amd64, the KEYWORDS would
be set to "x86" leaving amd64 compatibility indeterminate, but the -*
means "forget running this on anything else".


-- 
Neil Bothwick

PC DOS Error #04: Out of disk space. Delete Windows? (Y)es (H)ell yes!

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] espxe masked by missing keyword

[Friedrich Göpel]

On 8/9/06, Neil Bothwick <neil@digimed.co.uk> wrote:
>
> See the documentation mentioned above. In this case, both the ebuilds
> contain KEYWORDS="-* x86". this means they only run on x86 (the -*
> explicitly excludes everything else). You mentioned in your other post
> that you are using amd64, it appear this package will not run on amd64.
>
> If it was simply a case of not being tested on amd64, the KEYWORDS would
> be set to "x86" leaving amd64 compatibility indeterminate, but the -*
> means "forget running this on anything else".
>

Yeah well, except that it's a lie and runs just fine on amd64, you
just need the relevant emul- packages.
The only thing you need to watch out for is that if you're trying to
use one of the few plugins that actually come with sourcecode that
they need to be compiled for 32 bit.

It's a big mystery to me why this isn't in the tree, they could always
not put the amd64 keyword in the source based plugins if noone wants
to fix the ebuilds...
Not to sound ungrateful or anything, but still...this sucks.

For epsxe it should be enough to put "games-emulation/epsxe -*" in
/etc/portage/package.keywords
(Or better just use the ebuild from here:
http://bugs.gentoo.org/show_bug.cgi?id=104751
Since this takes care of the emul- dependencies too, so you don't have to)

The same for the binary plugins like eternalspu and pete's gpu plugins.
Only the the plugins which are compiled like peops-spu would be a bit
more difficult, as you need to compile them for 32 bit to work with
your 32 bit epsxe binary.
You should take a look at the zsnes ebuild to see what would need to
be changed if you want to do it gentoo style per ebuild.
(Sticking "use amd64 && multilib_toolchain_setup x86" in  the top of
src_compile should be enough)

If this doesn't work right for some reason or other, you have to
compile manually, exporting ABI=32 and putting -m32 in your CFLAGS,
which should do the trick.


I'm not using any of the compiled ones atm and am not at home right
now, but if you need any help with that I might be able to provide it
later.

Cheers,

Friedrich Göpel

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] espxe masked by missing keyword

[Andrew Syrewicze]

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

Thanks for the replies all.

well instead of using the 64bit version of the program, is it possible to
emerge the x86?? I know that there are 32bit compatability packages that
allow you to run programs like this. (firefox-bin for example).  is it
possible to mix in packages for other architecture like that???  Or maybe
setup a 32bit chroot to run the program in???

correct me if i'm wrong, but the problem is with the plugins not the program
correct???

if not I will add the neccessary entries to  /etc/portage/package.keywords
file and  emerge it when I get home from work and compile away from there
:-D.



On 8/9/06, Friedrich Göpel <shado23@gmail.com> wrote:
>
> On 8/9/06, Neil Bothwick <neil@digimed.co.uk> wrote:
> >
> > See the documentation mentioned above. In this case, both the ebuilds
> > contain KEYWORDS="-* x86". this means they only run on x86 (the -*
> > explicitly excludes everything else). You mentioned in your other post
> > that you are using amd64, it appear this package will not run on amd64.
> >
> > If it was simply a case of not being tested on amd64, the KEYWORDS would
> > be set to "x86" leaving amd64 compatibility indeterminate, but the -*
> > means "forget running this on anything else".
> >
>
> Yeah well, except that it's a lie and runs just fine on amd64, you
> just need the relevant emul- packages.
> The only thing you need to watch out for is that if you're trying to
> use one of the few plugins that actually come with sourcecode that
> they need to be compiled for 32 bit.
>
> It's a big mystery to me why this isn't in the tree, they could always
> not put the amd64 keyword in the source based plugins if noone wants
> to fix the ebuilds...
> Not to sound ungrateful or anything, but still...this sucks.
>
> For epsxe it should be enough to put "games-emulation/epsxe -*" in
> /etc/portage/package.keywords
> (Or better just use the ebuild from here:
> http://bugs.gentoo.org/show_bug.cgi?id=104751
> Since this takes care of the emul- dependencies too, so you don't have to)
>
> The same for the binary plugins like eternalspu and pete's gpu plugins.
> Only the the plugins which are compiled like peops-spu would be a bit
> more difficult, as you need to compile them for 32 bit to work with
> your 32 bit epsxe binary.
> You should take a look at the zsnes ebuild to see what would need to
> be changed if you want to do it gentoo style per ebuild.
> (Sticking "use amd64 && multilib_toolchain_setup x86" in  the top of
> src_compile should be enough)
>
> If this doesn't work right for some reason or other, you have to
> compile manually, exporting ABI=32 and putting -m32 in your CFLAGS,
> which should do the trick.
>
>
> I'm not using any of the compiled ones atm and am not at home right
> now, but if you need any help with that I might be able to provide it
> later.
>
> Cheers,
>
> Friedrich Göpel
>
> --
> gentoo-user@gentoo.org mailing list
>
>


-- 
   -Andrew Syrewicze

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

Re: [gentoo-user] espxe masked by missing keyword

[Neil Bothwick]

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

On Wed, 9 Aug 2006 10:36:39 -0400, Andrew Syrewicze wrote:

> well instead of using the 64bit version of the program, is it possible
> to emerge the x86?? I know that there are 32bit compatability packages
> that allow you to run programs like this. (firefox-bin for example).
> is it possible to mix in packages for other architecture like that???
> Or maybe setup a 32bit chroot to run the program in???

There is no 64 bit version of the program, only a pre-compiled 32 bit
executable, which is probably why it is masked for anything but x86.
however, as others have found, it does run on an amd64 system. 


-- 
Neil Bothwick

Never drink coffee that's been anywhere near a fish.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] espxe masked by missing keyword

[Friedrich Göpel]

On 8/9/06, Neil Bothwick <neil@digimed.co.uk> wrote:
> On Wed, 9 Aug 2006 10:36:39 -0400, Andrew Syrewicze wrote:
>
> > well instead of using the 64bit version of the program, is it possible
> > to emerge the x86?? I know that there are 32bit compatability packages
> > that allow you to run programs like this. (firefox-bin for example).
> > is it possible to mix in packages for other architecture like that???
> > Or maybe setup a 32bit chroot to run the program in???
>
Mixing is in this case ok, because amd64 is a special case because it
features 32 bit x86 compatibility so you can do that.
Also you really don't need to waste all that space and time for a chroot,
x86_64 gcc is capable of producing 32 bit code, which just leaves that
you need to have the libraries it links against in 32 bit, most of the
plugins for epsxe  and epsxe itself are binary only and are already 32
bit.
And that's what the emul-linux-x86-* packages are for, they are
provided so you don't need to compile them  yourself and also because
portage has no proper crosscompiling support yet.

For instance you will need emul-linux-x86-sdl for psemu-eternalspu,
normally portage would do that for you, but since these packages
aren't amd64-aware they don't automatically pull that in.

So basically if you just want a working epsxe just install epsxe,
psemu-eternalspu and psemu-gpupetexgl2 (after doing the keyword thing)
and worry about the rest later.

Note, that epsxe 1.6.0 has nasty slowdown bug that hits the final
fantasy games and some others, but 1.5.2 works fine in this regard.

If you run into any problems along the way, just ask.

> There is no 64 bit version of the program, only a pre-compiled 32 bit
> executable, which is probably why it is masked for anything but x86.
> however, as others have found, it does run on an amd64 system.
>
Yup, what he said.

Cheers,

Friedrich Göpel

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] espxe masked by missing keyword

[Andrew Syrewicze]

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

cool, thx for the help, I'll give it a try when I get home tonight.

I figured something like that would work cause I used to do similar things
on debian. of course i've long since left debian for gentoo. :-)  I like
gentoo MUCH better.

thanks guys

-A

On 8/9/06, Friedrich Göpel <shado23@gmail.com> wrote:
>
> On 8/9/06, Neil Bothwick <neil@digimed.co.uk> wrote:
> > On Wed, 9 Aug 2006 10:36:39 -0400, Andrew Syrewicze wrote:
> >
> > > well instead of using the 64bit version of the program, is it possible
> > > to emerge the x86?? I know that there are 32bit compatability packages
> > > that allow you to run programs like this. (firefox-bin for example).
> > > is it possible to mix in packages for other architecture like that???
> > > Or maybe setup a 32bit chroot to run the program in???
> >
> Mixing is in this case ok, because amd64 is a special case because it
> features 32 bit x86 compatibility so you can do that.
> Also you really don't need to waste all that space and time for a chroot,
> x86_64 gcc is capable of producing 32 bit code, which just leaves that
> you need to have the libraries it links against in 32 bit, most of the
> plugins for epsxe  and epsxe itself are binary only and are already 32
> bit.
> And that's what the emul-linux-x86-* packages are for, they are
> provided so you don't need to compile them  yourself and also because
> portage has no proper crosscompiling support yet.
>
> For instance you will need emul-linux-x86-sdl for psemu-eternalspu,
> normally portage would do that for you, but since these packages
> aren't amd64-aware they don't automatically pull that in.
>
> So basically if you just want a working epsxe just install epsxe,
> psemu-eternalspu and psemu-gpupetexgl2 (after doing the keyword thing)
> and worry about the rest later.
>
> Note, that epsxe 1.6.0 has nasty slowdown bug that hits the final
> fantasy games and some others, but 1.5.2 works fine in this regard.
>
> If you run into any problems along the way, just ask.
>
> > There is no 64 bit version of the program, only a pre-compiled 32 bit
> > executable, which is probably why it is masked for anything but x86.
> > however, as others have found, it does run on an amd64 system.
> >
> Yup, what he said.
>
> Cheers,
>
> Friedrich Göpel
>
> --
> gentoo-user@gentoo.org mailing list
>
>


-- 
   -Andrew Syrewicze

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