Github messages for voidlinux
 help / Atom feed
* [PR PATCH] libretro-mupen64plus: update to 20190611
@ 2019-06-11 15:53 voidlinux-github
  2019-06-11 15:54 ` [PR PATCH] [Updated] " voidlinux-github
                   ` (24 more replies)
  0 siblings, 25 replies; 26+ messages in thread
From: voidlinux-github @ 2019-06-11 15:53 UTC (permalink / raw)
  To: ml

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

There is a new pull request by q66 against master on the void-packages repository

https://github.com/void-power/void-packages libretro-mupen64plus
https://github.com/void-linux/void-packages/pull/12400

libretro-mupen64plus: update to 20190611
Our 2015something version is aging and I don't think it's worth it to do any more fixes on it, especially considering there have been many commits upstream since and updating also allows building on ppc platforms and so on. However, there are no releases, ever, so trying a github commit snapshot (dunno if that's the right thing to do, but it can't be worse than using a random netbsd distfile...)

I also wonder if the default `rpi` option for armv6/7 is right, as that will make it not work on anything but... rpi, which is not exactly a generic target, we have many different ones now. Maybe we should switch that to standard mesa opengl. Thoughts?

A patch file from https://github.com/void-linux/void-packages/pull/12400.patch is attached

[-- Attachment #2: github-pr-libretro-mupen64plus-12400.patch --]
[-- Type: application/text/x-diff, Size: 2506 bytes --]

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: [PR PATCH] [Updated] libretro-mupen64plus: update to 20190611
  2019-06-11 15:53 [PR PATCH] libretro-mupen64plus: update to 20190611 voidlinux-github
@ 2019-06-11 15:54 ` " voidlinux-github
  2019-06-11 16:20 ` voidlinux-github
                   ` (23 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: voidlinux-github @ 2019-06-11 15:54 UTC (permalink / raw)
  To: ml

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

There is an updated pull request by q66 against master on the void-packages repository

https://github.com/void-power/void-packages libretro-mupen64plus
https://github.com/void-linux/void-packages/pull/12400

libretro-mupen64plus: update to 20190611
Our 2015something version is aging and I don't think it's worth it to do any more fixes on it, especially considering there have been many commits upstream since and updating also allows building on ppc platforms and so on. However, there are no releases, ever, so trying a github commit snapshot (dunno if that's the right thing to do, but it can't be worse than using a random netbsd distfile...)

I also wonder if the default `rpi` option for armv6/7 is right, as that will make it not work on anything but... rpi, which is not exactly a generic target, we have many different ones now. Maybe we should switch that to standard mesa opengl. Thoughts?

A patch file from https://github.com/void-linux/void-packages/pull/12400.patch is attached

[-- Attachment #2: github-pr-libretro-mupen64plus-12400.patch --]
[-- Type: application/text/x-diff, Size: 2555 bytes --]

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: [PR PATCH] [Updated] libretro-mupen64plus: update to 20190611
  2019-06-11 15:53 [PR PATCH] libretro-mupen64plus: update to 20190611 voidlinux-github
  2019-06-11 15:54 ` [PR PATCH] [Updated] " voidlinux-github
@ 2019-06-11 16:20 ` voidlinux-github
  2019-06-11 16:21 ` voidlinux-github
                   ` (22 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: voidlinux-github @ 2019-06-11 16:20 UTC (permalink / raw)
  To: ml

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

There is an updated pull request by q66 against master on the void-packages repository

https://github.com/void-power/void-packages libretro-mupen64plus
https://github.com/void-linux/void-packages/pull/12400

libretro-mupen64plus: update to 20190611
Our 2015something version is aging and I don't think it's worth it to do any more fixes on it, especially considering there have been many commits upstream since and updating also allows building on ppc platforms and so on. However, there are no releases, ever, so trying a github commit snapshot (dunno if that's the right thing to do, but it can't be worse than using a random netbsd distfile...)

I also wonder if the default `rpi` option for armv6/7 is right, as that will make it not work on anything but... rpi, which is not exactly a generic target, we have many different ones now. Maybe we should switch that to standard mesa opengl. Thoughts?

I tested cross-compiling to aarch64, but not the others. I'll let the CI handle that.

A patch file from https://github.com/void-linux/void-packages/pull/12400.patch is attached

[-- Attachment #2: github-pr-libretro-mupen64plus-12400.patch --]
[-- Type: application/text/x-diff, Size: 2501 bytes --]

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: libretro-mupen64plus: update to 20190611
  2019-06-11 15:53 [PR PATCH] libretro-mupen64plus: update to 20190611 voidlinux-github
  2019-06-11 15:54 ` [PR PATCH] [Updated] " voidlinux-github
  2019-06-11 16:20 ` voidlinux-github
@ 2019-06-11 16:21 ` voidlinux-github
  2019-06-11 16:41 ` [PR PATCH] [Updated] " voidlinux-github
                   ` (21 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: voidlinux-github @ 2019-06-11 16:21 UTC (permalink / raw)
  To: ml

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

New comment by q66 on void-packages repository

https://github.com/void-linux/void-packages/pull/12400#issuecomment-500917123
Comment:
Turns out MesaLib-devel is required for OpenGL(ES) headers every time, so removed the `opengl` option and made it implicit. Also we needed `nasm` for i686 in `hostmakedepends`.

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: [PR PATCH] [Updated] libretro-mupen64plus: update to 20190611
  2019-06-11 15:53 [PR PATCH] libretro-mupen64plus: update to 20190611 voidlinux-github
                   ` (2 preceding siblings ...)
  2019-06-11 16:21 ` voidlinux-github
@ 2019-06-11 16:41 ` " voidlinux-github
  2019-06-11 16:42 ` voidlinux-github
                   ` (20 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: voidlinux-github @ 2019-06-11 16:41 UTC (permalink / raw)
  To: ml

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

There is an updated pull request by q66 against master on the void-packages repository

https://github.com/void-power/void-packages libretro-mupen64plus
https://github.com/void-linux/void-packages/pull/12400

libretro-mupen64plus: update to 20190611
Our 2015something version is aging and I don't think it's worth it to do any more fixes on it, especially considering there have been many commits upstream since and updating also allows building on ppc platforms and so on. However, there are no releases, ever, so trying a github commit snapshot (dunno if that's the right thing to do, but it can't be worse than using a random netbsd distfile...)

I also wonder if the default `rpi` option for armv6/7 is right, as that will make it not work on anything but... rpi, which is not exactly a generic target, we have many different ones now. Maybe we should switch that to standard mesa opengl. Thoughts?

I tested cross-compiling to aarch64, but not the others. I'll let the CI handle that.

A patch file from https://github.com/void-linux/void-packages/pull/12400.patch is attached

[-- Attachment #2: github-pr-libretro-mupen64plus-12400.patch --]
[-- Type: application/text/x-diff, Size: 2666 bytes --]

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: libretro-mupen64plus: update to 20190611
  2019-06-11 15:53 [PR PATCH] libretro-mupen64plus: update to 20190611 voidlinux-github
                   ` (3 preceding siblings ...)
  2019-06-11 16:41 ` [PR PATCH] [Updated] " voidlinux-github
@ 2019-06-11 16:42 ` voidlinux-github
  2019-06-11 17:02 ` [PR PATCH] [Updated] " voidlinux-github
                   ` (19 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: voidlinux-github @ 2019-06-11 16:42 UTC (permalink / raw)
  To: ml

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

New comment by q66 on void-packages repository

https://github.com/void-linux/void-packages/pull/12400#issuecomment-500926143
Comment:
Seems almost fine, though there was one more fix needed, to prevent a conflicting typedef. Let's see now.

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: [PR PATCH] [Updated] libretro-mupen64plus: update to 20190611
  2019-06-11 15:53 [PR PATCH] libretro-mupen64plus: update to 20190611 voidlinux-github
                   ` (4 preceding siblings ...)
  2019-06-11 16:42 ` voidlinux-github
@ 2019-06-11 17:02 ` " voidlinux-github
  2019-06-11 17:03 ` voidlinux-github
                   ` (18 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: voidlinux-github @ 2019-06-11 17:02 UTC (permalink / raw)
  To: ml

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

There is an updated pull request by q66 against master on the void-packages repository

https://github.com/void-power/void-packages libretro-mupen64plus
https://github.com/void-linux/void-packages/pull/12400

libretro-mupen64plus: update to 20190611
Our 2015something version is aging and I don't think it's worth it to do any more fixes on it, especially considering there have been many commits upstream since and updating also allows building on ppc platforms and so on. However, there are no releases, ever, so trying a github commit snapshot (dunno if that's the right thing to do, but it can't be worse than using a random netbsd distfile...)

I also wonder if the default `rpi` option for armv6/7 is right, as that will make it not work on anything but... rpi, which is not exactly a generic target, we have many different ones now. Maybe we should switch that to standard mesa opengl. Thoughts?

I tested cross-compiling to aarch64, but not the others. I'll let the CI handle that.

A patch file from https://github.com/void-linux/void-packages/pull/12400.patch is attached

[-- Attachment #2: github-pr-libretro-mupen64plus-12400.patch --]
[-- Type: application/text/x-diff, Size: 3821 bytes --]

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: libretro-mupen64plus: update to 20190611
  2019-06-11 15:53 [PR PATCH] libretro-mupen64plus: update to 20190611 voidlinux-github
                   ` (5 preceding siblings ...)
  2019-06-11 17:02 ` [PR PATCH] [Updated] " voidlinux-github
@ 2019-06-11 17:03 ` voidlinux-github
  2019-06-11 17:25 ` [PR PATCH] [Updated] " voidlinux-github
                   ` (17 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: voidlinux-github @ 2019-06-11 17:03 UTC (permalink / raw)
  To: ml

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

New comment by q66 on void-packages repository

https://github.com/void-linux/void-packages/pull/12400#issuecomment-500934670
Comment:
OK, trying one more thing... also added options for gles/gles3

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: [PR PATCH] [Updated] libretro-mupen64plus: update to 20190611
  2019-06-11 15:53 [PR PATCH] libretro-mupen64plus: update to 20190611 voidlinux-github
                   ` (6 preceding siblings ...)
  2019-06-11 17:03 ` voidlinux-github
@ 2019-06-11 17:25 ` " voidlinux-github
  2019-06-11 17:33 ` voidlinux-github
                   ` (16 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: voidlinux-github @ 2019-06-11 17:25 UTC (permalink / raw)
  To: ml

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

There is an updated pull request by q66 against master on the void-packages repository

https://github.com/void-power/void-packages libretro-mupen64plus
https://github.com/void-linux/void-packages/pull/12400

libretro-mupen64plus: update to 20190611
Our 2015something version is aging and I don't think it's worth it to do any more fixes on it, especially considering there have been many commits upstream since and updating also allows building on ppc platforms and so on. However, there are no releases, ever, so trying a github commit snapshot (dunno if that's the right thing to do, but it can't be worse than using a random netbsd distfile...)

I also wonder if the default `rpi` option for armv6/7 is right, as that will make it not work on anything but... rpi, which is not exactly a generic target, we have many different ones now. Maybe we should switch that to standard mesa opengl. Thoughts?

I tested cross-compiling to aarch64, but not the others. I'll let the CI handle that.

A patch file from https://github.com/void-linux/void-packages/pull/12400.patch is attached

[-- Attachment #2: github-pr-libretro-mupen64plus-12400.patch --]
[-- Type: application/text/x-diff, Size: 4153 bytes --]

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: libretro-mupen64plus: update to 20190611
  2019-06-11 15:53 [PR PATCH] libretro-mupen64plus: update to 20190611 voidlinux-github
                   ` (7 preceding siblings ...)
  2019-06-11 17:25 ` [PR PATCH] [Updated] " voidlinux-github
@ 2019-06-11 17:33 ` voidlinux-github
  2019-06-11 17:33 ` voidlinux-github
                   ` (15 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: voidlinux-github @ 2019-06-11 17:33 UTC (permalink / raw)
  To: ml

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

New comment by q66 on void-packages repository

https://github.com/void-linux/void-packages/pull/12400#issuecomment-500917123
Comment:
Turns out MesaLib-devel is required for OpenGL(ES) headers every time, so removed the `opengl` option and made it implicit. Also we needed `nasm` for i686 in `hostmakedepends`.

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: libretro-mupen64plus: update to 20190611
  2019-06-11 15:53 [PR PATCH] libretro-mupen64plus: update to 20190611 voidlinux-github
                   ` (8 preceding siblings ...)
  2019-06-11 17:33 ` voidlinux-github
@ 2019-06-11 17:33 ` voidlinux-github
  2019-06-11 17:33 ` voidlinux-github
                   ` (14 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: voidlinux-github @ 2019-06-11 17:33 UTC (permalink / raw)
  To: ml

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

New comment by q66 on void-packages repository

https://github.com/void-linux/void-packages/pull/12400#issuecomment-500926143
Comment:
Seems almost fine, though there was one more fix needed, to prevent a conflicting typedef. Let's see now.

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: libretro-mupen64plus: update to 20190611
  2019-06-11 15:53 [PR PATCH] libretro-mupen64plus: update to 20190611 voidlinux-github
                   ` (9 preceding siblings ...)
  2019-06-11 17:33 ` voidlinux-github
@ 2019-06-11 17:33 ` voidlinux-github
  2019-06-11 17:36 ` voidlinux-github
                   ` (13 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: voidlinux-github @ 2019-06-11 17:33 UTC (permalink / raw)
  To: ml

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

New comment by q66 on void-packages repository

https://github.com/void-linux/void-packages/pull/12400#issuecomment-500934670
Comment:
OK, trying one more thing... also added options for gles/gles3

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: libretro-mupen64plus: update to 20190611
  2019-06-11 15:53 [PR PATCH] libretro-mupen64plus: update to 20190611 voidlinux-github
                   ` (10 preceding siblings ...)
  2019-06-11 17:33 ` voidlinux-github
@ 2019-06-11 17:36 ` voidlinux-github
  2019-06-11 17:44 ` voidlinux-github
                   ` (12 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: voidlinux-github @ 2019-06-11 17:36 UTC (permalink / raw)
  To: ml

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

New comment by q66 on void-packages repository

https://github.com/void-linux/void-packages/pull/12400#issuecomment-500947458
Comment:
Looks like this is now fixed. Total change log:

- Added new build options `gles`, `gles3` which force GLES2 and GLES3 respectively when used with `opengl`.
- Made it possible to use `opengl` with `rpi`, which effectively uses Mesa (setting `platform=rpi,mesa` for the build)
- Fixed `rpi` (needed to install `rpi-userland-devel` instead of `rpi-firmware`)
- Fixed i686 (needed to install `nasm` on host)
- `aarch64` uses GLES2
- `armv6/7` uses rpi (i.e. as before)
- everything else uses standard OpenGL, and all platforms are now enabled.

Questions:

- Since raspberry pi is hardly a generic target, should we remove it and create a separate `-rpi` suffixed package for that, then use the same settings on `armv*` and `aarch64*`? We already have this elsewhere; see e.g. `EmulationStation` and `EmulationStation-rpi`.

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: libretro-mupen64plus: update to 20190611
  2019-06-11 15:53 [PR PATCH] libretro-mupen64plus: update to 20190611 voidlinux-github
                   ` (11 preceding siblings ...)
  2019-06-11 17:36 ` voidlinux-github
@ 2019-06-11 17:44 ` voidlinux-github
  2019-06-11 17:51 ` [PR PATCH] [Updated] " voidlinux-github
                   ` (11 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: voidlinux-github @ 2019-06-11 17:44 UTC (permalink / raw)
  To: ml

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

New comment by q66 on void-packages repository

https://github.com/void-linux/void-packages/pull/12400#issuecomment-500950132
Comment:
(though looks like `new_dynarec` is still failing on `musl` because it uses glibc internal types... sigh)

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: [PR PATCH] [Updated] libretro-mupen64plus: update to 20190611
  2019-06-11 15:53 [PR PATCH] libretro-mupen64plus: update to 20190611 voidlinux-github
                   ` (12 preceding siblings ...)
  2019-06-11 17:44 ` voidlinux-github
@ 2019-06-11 17:51 ` " voidlinux-github
  2019-06-11 18:50 ` voidlinux-github
                   ` (10 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: voidlinux-github @ 2019-06-11 17:51 UTC (permalink / raw)
  To: ml

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

There is an updated pull request by q66 against master on the void-packages repository

https://github.com/void-power/void-packages libretro-mupen64plus
https://github.com/void-linux/void-packages/pull/12400

libretro-mupen64plus: update to 20190611
Our 2015something version is aging and I don't think it's worth it to do any more fixes on it, especially considering there have been many commits upstream since and updating also allows building on ppc platforms and so on. However, there are no releases, ever, so trying a github commit snapshot (dunno if that's the right thing to do, but it can't be worse than using a random netbsd distfile...)

I also wonder if the default `rpi` option for armv6/7 is right, as that will make it not work on anything but... rpi, which is not exactly a generic target, we have many different ones now. Maybe we should switch that to standard mesa opengl. Thoughts?

I tested cross-compiling to aarch64, but not the others. I'll let the CI handle that.

A patch file from https://github.com/void-linux/void-packages/pull/12400.patch is attached

[-- Attachment #2: github-pr-libretro-mupen64plus-12400.patch --]
[-- Type: application/text/x-diff, Size: 5306 bytes --]

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: libretro-mupen64plus: update to 20190611
  2019-06-11 15:53 [PR PATCH] libretro-mupen64plus: update to 20190611 voidlinux-github
                   ` (13 preceding siblings ...)
  2019-06-11 17:51 ` [PR PATCH] [Updated] " voidlinux-github
@ 2019-06-11 18:50 ` voidlinux-github
  2019-06-11 19:36 ` [PR PATCH] [Updated] " voidlinux-github
                   ` (9 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: voidlinux-github @ 2019-06-11 18:50 UTC (permalink / raw)
  To: ml

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

New comment by q66 on void-packages repository

https://github.com/void-linux/void-packages/pull/12400#issuecomment-500975163
Comment:
Seems fixed now. Only the above remains

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: [PR PATCH] [Updated] libretro-mupen64plus: update to 20190611
  2019-06-11 15:53 [PR PATCH] libretro-mupen64plus: update to 20190611 voidlinux-github
                   ` (14 preceding siblings ...)
  2019-06-11 18:50 ` voidlinux-github
@ 2019-06-11 19:36 ` " voidlinux-github
  2019-06-11 19:36 ` voidlinux-github
                   ` (8 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: voidlinux-github @ 2019-06-11 19:36 UTC (permalink / raw)
  To: ml

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

There is an updated pull request by q66 against master on the void-packages repository

https://github.com/void-power/void-packages libretro-mupen64plus
https://github.com/void-linux/void-packages/pull/12400

libretro-mupen64plus: update to 20190611
Our 2015something version is aging and I don't think it's worth it to do any more fixes on it, especially considering there have been many commits upstream since and updating also allows building on ppc platforms and so on. However, there are no releases, ever, so trying a github commit snapshot (dunno if that's the right thing to do, but it can't be worse than using a random netbsd distfile...)

I also wonder if the default `rpi` option for armv6/7 is right, as that will make it not work on anything but... rpi, which is not exactly a generic target, we have many different ones now. Maybe we should switch that to standard mesa opengl. Thoughts?

I tested cross-compiling to aarch64, but not the others. I'll let the CI handle that.

A patch file from https://github.com/void-linux/void-packages/pull/12400.patch is attached

[-- Attachment #2: github-pr-libretro-mupen64plus-12400.patch --]
[-- Type: application/text/x-diff, Size: 9043 bytes --]

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: libretro-mupen64plus: update to 20190611
  2019-06-11 15:53 [PR PATCH] libretro-mupen64plus: update to 20190611 voidlinux-github
                   ` (15 preceding siblings ...)
  2019-06-11 19:36 ` [PR PATCH] [Updated] " voidlinux-github
@ 2019-06-11 19:36 ` voidlinux-github
  2019-06-11 19:58 ` voidlinux-github
                   ` (7 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: voidlinux-github @ 2019-06-11 19:36 UTC (permalink / raw)
  To: ml

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

New comment by q66 on void-packages repository

https://github.com/void-linux/void-packages/pull/12400#issuecomment-500991653
Comment:
Trying the split.

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: libretro-mupen64plus: update to 20190611
  2019-06-11 15:53 [PR PATCH] libretro-mupen64plus: update to 20190611 voidlinux-github
                   ` (16 preceding siblings ...)
  2019-06-11 19:36 ` voidlinux-github
@ 2019-06-11 19:58 ` voidlinux-github
  2019-06-11 20:25 ` [PR PATCH] [Updated] " voidlinux-github
                   ` (6 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: voidlinux-github @ 2019-06-11 19:58 UTC (permalink / raw)
  To: ml

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

New comment by q66 on void-packages repository

https://github.com/void-linux/void-packages/pull/12400#issuecomment-500999823
Comment:
Looks like this works.

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: [PR PATCH] [Updated] libretro-mupen64plus: update to 20190611
  2019-06-11 15:53 [PR PATCH] libretro-mupen64plus: update to 20190611 voidlinux-github
                   ` (17 preceding siblings ...)
  2019-06-11 19:58 ` voidlinux-github
@ 2019-06-11 20:25 ` " voidlinux-github
  2019-06-11 21:06 ` voidlinux-github
                   ` (5 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: voidlinux-github @ 2019-06-11 20:25 UTC (permalink / raw)
  To: ml

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

There is an updated pull request by q66 against master on the void-packages repository

https://github.com/void-power/void-packages libretro-mupen64plus
https://github.com/void-linux/void-packages/pull/12400

libretro-mupen64plus: update to 20190611
Our 2015something version is aging and I don't think it's worth it to do any more fixes on it, especially considering there have been many commits upstream since and updating also allows building on ppc platforms and so on. However, there are no releases, ever, so trying a github commit snapshot (dunno if that's the right thing to do, but it can't be worse than using a random netbsd distfile...)

I also wonder if the default `rpi` option for armv6/7 is right, as that will make it not work on anything but... rpi, which is not exactly a generic target, we have many different ones now. Maybe we should switch that to standard mesa opengl. Thoughts?

I tested cross-compiling to aarch64, but not the others. I'll let the CI handle that.

A patch file from https://github.com/void-linux/void-packages/pull/12400.patch is attached

[-- Attachment #2: github-pr-libretro-mupen64plus-12400.patch --]
[-- Type: application/text/x-diff, Size: 9029 bytes --]

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: libretro-mupen64plus: update to 20190611
  2019-06-11 15:53 [PR PATCH] libretro-mupen64plus: update to 20190611 voidlinux-github
                   ` (18 preceding siblings ...)
  2019-06-11 20:25 ` [PR PATCH] [Updated] " voidlinux-github
@ 2019-06-11 21:06 ` voidlinux-github
  2019-06-11 21:06 ` voidlinux-github
                   ` (4 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: voidlinux-github @ 2019-06-11 21:06 UTC (permalink / raw)
  To: ml

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

New comment by q66 on void-packages repository

https://github.com/void-linux/void-packages/pull/12400#issuecomment-500950132
Comment:
(though looks like `new_dynarec` is still failing on `musl` because it uses glibc internal types... sigh)

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: libretro-mupen64plus: update to 20190611
  2019-06-11 15:53 [PR PATCH] libretro-mupen64plus: update to 20190611 voidlinux-github
                   ` (19 preceding siblings ...)
  2019-06-11 21:06 ` voidlinux-github
@ 2019-06-11 21:06 ` voidlinux-github
  2019-06-11 21:06 ` voidlinux-github
                   ` (3 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: voidlinux-github @ 2019-06-11 21:06 UTC (permalink / raw)
  To: ml

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

New comment by q66 on void-packages repository

https://github.com/void-linux/void-packages/pull/12400#issuecomment-500975163
Comment:
Seems fixed now. Only the above remains

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: libretro-mupen64plus: update to 20190611
  2019-06-11 15:53 [PR PATCH] libretro-mupen64plus: update to 20190611 voidlinux-github
                   ` (20 preceding siblings ...)
  2019-06-11 21:06 ` voidlinux-github
@ 2019-06-11 21:06 ` voidlinux-github
  2019-06-11 21:06 ` voidlinux-github
                   ` (2 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: voidlinux-github @ 2019-06-11 21:06 UTC (permalink / raw)
  To: ml

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

New comment by q66 on void-packages repository

https://github.com/void-linux/void-packages/pull/12400#issuecomment-500991653
Comment:
Trying the split.

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: libretro-mupen64plus: update to 20190611
  2019-06-11 15:53 [PR PATCH] libretro-mupen64plus: update to 20190611 voidlinux-github
                   ` (21 preceding siblings ...)
  2019-06-11 21:06 ` voidlinux-github
@ 2019-06-11 21:06 ` voidlinux-github
  2019-06-11 21:08 ` voidlinux-github
  2019-06-15 12:43 ` [PR PATCH] [Merged]: " voidlinux-github
  24 siblings, 0 replies; 26+ messages in thread
From: voidlinux-github @ 2019-06-11 21:06 UTC (permalink / raw)
  To: ml

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

New comment by q66 on void-packages repository

https://github.com/void-linux/void-packages/pull/12400#issuecomment-500999823
Comment:
Looks like this works.

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: libretro-mupen64plus: update to 20190611
  2019-06-11 15:53 [PR PATCH] libretro-mupen64plus: update to 20190611 voidlinux-github
                   ` (22 preceding siblings ...)
  2019-06-11 21:06 ` voidlinux-github
@ 2019-06-11 21:08 ` voidlinux-github
  2019-06-15 12:43 ` [PR PATCH] [Merged]: " voidlinux-github
  24 siblings, 0 replies; 26+ messages in thread
From: voidlinux-github @ 2019-06-11 21:08 UTC (permalink / raw)
  To: ml

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

New comment by q66 on void-packages repository

https://github.com/void-linux/void-packages/pull/12400#issuecomment-500947458
Comment:
Looks like this is now fixed. Total change log:

- Fixed the Raspberry Pi build and split into `libretro-mupen64plus` and `libretro-mupen64plus-rpi`; the former is generic, the latter is only for `armv6*` and `armv7*`, compiling with rpi specific platform (`rpi2` for `armv7*`)
- Added new build options `gles`, `gles3` which force GLES2 and GLES3 respectively; `opengl` is implicit/default for the standard package
- Fixed i686 (needed to install `nasm` on host)
- `aarch64` uses GLES2, as does `armv*` in the standard package
- everything else uses standard desktop OpenGL, and all platforms are now enabled.


^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: [PR PATCH] [Merged]: libretro-mupen64plus: update to 20190611
  2019-06-11 15:53 [PR PATCH] libretro-mupen64plus: update to 20190611 voidlinux-github
                   ` (23 preceding siblings ...)
  2019-06-11 21:08 ` voidlinux-github
@ 2019-06-15 12:43 ` " voidlinux-github
  24 siblings, 0 replies; 26+ messages in thread
From: voidlinux-github @ 2019-06-15 12:43 UTC (permalink / raw)
  To: ml

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

There's a merged pull request on the void-packages repository

libretro-mupen64plus: update to 20190611
https://github.com/void-linux/void-packages/pull/12400
Description: Our 2015something version is aging and I don't think it's worth it to do any more fixes on it, especially considering there have been many commits upstream since and updating also allows building on ppc platforms and so on. However, there are no releases, ever, so trying a github commit snapshot (dunno if that's the right thing to do, but it can't be worse than using a random netbsd distfile...)

I also wonder if the default `rpi` option for armv6/7 is right, as that will make it not work on anything but... rpi, which is not exactly a generic target, we have many different ones now. Maybe we should switch that to standard mesa opengl. Thoughts?

I tested cross-compiling to aarch64, but not the others. I'll let the CI handle that.

^ permalink raw reply	[flat|nested] 26+ messages in thread

end of thread, back to index

Thread overview: 26+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-06-11 15:53 [PR PATCH] libretro-mupen64plus: update to 20190611 voidlinux-github
2019-06-11 15:54 ` [PR PATCH] [Updated] " voidlinux-github
2019-06-11 16:20 ` voidlinux-github
2019-06-11 16:21 ` voidlinux-github
2019-06-11 16:41 ` [PR PATCH] [Updated] " voidlinux-github
2019-06-11 16:42 ` voidlinux-github
2019-06-11 17:02 ` [PR PATCH] [Updated] " voidlinux-github
2019-06-11 17:03 ` voidlinux-github
2019-06-11 17:25 ` [PR PATCH] [Updated] " voidlinux-github
2019-06-11 17:33 ` voidlinux-github
2019-06-11 17:33 ` voidlinux-github
2019-06-11 17:33 ` voidlinux-github
2019-06-11 17:36 ` voidlinux-github
2019-06-11 17:44 ` voidlinux-github
2019-06-11 17:51 ` [PR PATCH] [Updated] " voidlinux-github
2019-06-11 18:50 ` voidlinux-github
2019-06-11 19:36 ` [PR PATCH] [Updated] " voidlinux-github
2019-06-11 19:36 ` voidlinux-github
2019-06-11 19:58 ` voidlinux-github
2019-06-11 20:25 ` [PR PATCH] [Updated] " voidlinux-github
2019-06-11 21:06 ` voidlinux-github
2019-06-11 21:06 ` voidlinux-github
2019-06-11 21:06 ` voidlinux-github
2019-06-11 21:06 ` voidlinux-github
2019-06-11 21:08 ` voidlinux-github
2019-06-15 12:43 ` [PR PATCH] [Merged]: " voidlinux-github

Github messages for voidlinux

Archives are clonable: git clone --mirror http://inbox.vuxu.org/voidlinux-github

Newsgroup available over NNTP:
	nntp://inbox.vuxu.org/vuxu.github.voidlinux


AGPL code for this site: git clone https://public-inbox.org/ public-inbox