Re: Port OPTIONS advice
On Wednesday, 20 May 2020 18:25:00 BST SirDice wrote: > Some time ago I took over maintainership of fs-uae. And I'd like to thank you very much for that! :-) I finally got around to installing it, what with have an unexpected few spare months of time on my hands. I managed to dump my old A1200 HDD to a file and eventually got it to boot after a trip down memory lane figuring out how to edit startup-sequence and user-startup to remove things like the SCSI drivers. There was one issue when I upgraded FreeBSD 11.3 --> 11.4. fs-uae would crash out immediately the main window opened. Even after doing a pkg upgrade -f I still ended up having to manually build some related graphics libraries before it would work again (Sorry, I didn't keep notes, IIRC it was mesa stuff) So now all I need to do is find a cheap gamepad that will work with it on FreeBSD :-) If anyone is interested, you can download the Assassin Games CDs full of PD games from archive.org (and much other Amiga related goodness. They boot and play just fine on fs-uae assuming you have the correct ROM file(s)) Sorry if that last bit came over as a bit of a commercial but it's years since I even plugged my old A1200 in, let alone played games on it. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Port OPTIONS advice
On Wed, May 20, 2020 at 07:25:00PM +0200, SirDice wrote:
> What's a good way to deal with this sort of architecture dependent option?
If the feature is architecture dependant but also needs to be disabled
on architectures where it does not work, a naive way that I can see to
do it is probably to do something like this:
OPTIONS_DEFINE= JIT
OPTIONS_EXCLUDE_aarch64= JIT
OPTIONS_EXCLUDE_armv6= JIT
But you have to do it for all architectures, so it may not be the best
way, a way that would be a bit more convoluted, but still readable would
be:
OPTIONS_DEFINE= JIT
OPTIONS_EXCLUDE= ${ARCH:Ni386:Namd64:C/.+/JIT/}
What it does is take ARCH, remove i386 and amd64 from it, and there is
still something, replace it with JIT.
--
Mathieu Arnold
signature.asc
Description: PGP signature
Re: Port OPTIONS advice
On 20/05/2020 20:07, SirDice wrote: > On Wed, May 20, 2020 at 7:45 PM Martin Neubauer wrote: > >> How about something like: >> >> >> OPTIONS_DEFINE_amd64= JIT >> OPTIONS_DEFINE_i386=JIT >> >> JIT_CONFIGURE_ENABLE= jit >> >> >> That's what I had originally. The problem is that JIT_CONFIGURE_ENABLE is > only parsed on amd64/i386. So it never passes --without-jit to ./configure > on other architectures. > >> JIT_CONFIGURE_OFF= --without-jit > > Haven't tried that yet. But won't that suffer from the same effect, only > getting parsed if on amd64/i386? Honestly, I haven't tried it myself either, but judging from the usage of this method (eg. in /usr/ports/biology/mrbayes/Makefile) it at least seems to do just what you need. -- Shipwrecked by the laughter of the gods. signature.asc Description: OpenPGP digital signature
Re: Port OPTIONS advice
On 20/05/2020 19:45, Martin Neubauer wrote: > JIT_CONFIGURE_ENABLE= jit Sorry, JIT_CONFIGURE_OFF= --without-jit -- Mrs. Peacock in the study with a knife. signature.asc Description: OpenPGP digital signature
Re: Port OPTIONS advice
How about something like:
OPTIONS_DEFINE_amd64= JIT
OPTIONS_DEFINE_i386=JIT
JIT_CONFIGURE_ENABLE= jit
On 20/05/2020 19:25, SirDice wrote:
> Hi,
>
> Some time ago I took over maintainership of fs-uae. Port itself is doing
> great but I wanted to enable the JIT option to experiment with (it builds
> but crashes the application; that's an entirely different issue though). To
> enable it I had added this:
>
> OPTIONS_DEFINE_i386=JIT
> OPTIONS_DEFINE_amd64= JIT
>
> Because the option is only available for i386/amd64 I wanted the port
> option to only show up on x86. Unfortunately the brain-dead ./configure
> script simply assumes --with-jit on all architectures. As these OPTIONS
> were only available on x86, any other ARCH never passes --without-jit to
> ./configure and thus it fails to build.
>
> The quick solution was to use OPTIONS_DEFINE= JIT and make the port option
> available everywhere. However, if you try to enable it you will run into
> build failures on Powerpc or ARM for example.
>
> I could do this:
> -
> OPTIONS_DEFINE_i386=JIT
> OPTIONS_DEFINE_amd64= JIT
>
> .include
>
> # JIT is not supported on non-x86
> .if ${ARCH} != amd64 && ${ARCH} != i386
> CONFIGURE_ARGS+= --without-jit
> .endif
>
>
> Or do something like this:
>
> OPTIONS_DEFINE= JIT
>
> .include
>
> .if ${PORT_OPTIONS:MJIT}
> ONLY_FOR_ARCHS= i386 amd64
> .endif
>
>
>
> The JIT OPTION is off by default in all cases. But I would like to only
> have it appear on supported architectures or have some sort of sanity check
> so it doesn't get enabled on unsupported architectures. As I need to update
> the port (new version came out) I would like to fix this OPTION issue too.
>
> What's a good way to deal with this sort of architecture dependent option?
>
> Thanks for your time,
>
> Remko C.
> ___
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
>
--
Any environmental problem can be solved by a good Ice Age.
signature.asc
Description: OpenPGP digital signature
Port OPTIONS advice
Hi,
Some time ago I took over maintainership of fs-uae. Port itself is doing
great but I wanted to enable the JIT option to experiment with (it builds
but crashes the application; that's an entirely different issue though). To
enable it I had added this:
OPTIONS_DEFINE_i386=JIT
OPTIONS_DEFINE_amd64= JIT
Because the option is only available for i386/amd64 I wanted the port
option to only show up on x86. Unfortunately the brain-dead ./configure
script simply assumes --with-jit on all architectures. As these OPTIONS
were only available on x86, any other ARCH never passes --without-jit to
./configure and thus it fails to build.
The quick solution was to use OPTIONS_DEFINE= JIT and make the port option
available everywhere. However, if you try to enable it you will run into
build failures on Powerpc or ARM for example.
I could do this:
-
OPTIONS_DEFINE_i386=JIT
OPTIONS_DEFINE_amd64= JIT
.include
# JIT is not supported on non-x86
.if ${ARCH} != amd64 && ${ARCH} != i386
CONFIGURE_ARGS+= --without-jit
.endif
Or do something like this:
OPTIONS_DEFINE= JIT
.include
.if ${PORT_OPTIONS:MJIT}
ONLY_FOR_ARCHS= i386 amd64
.endif
The JIT OPTION is off by default in all cases. But I would like to only
have it appear on supported architectures or have some sort of sanity check
so it doesn't get enabled on unsupported architectures. As I need to update
the port (new version came out) I would like to fix this OPTION issue too.
What's a good way to deal with this sort of architecture dependent option?
Thanks for your time,
Remko C.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
