|
From: Philippe D. <phi...@la...> - 2025-11-10 23:31:50
|
Hi
Actually I have no problem to build the last version of LinuxSampler
(2.4.1) for the existing version of my distribution
using GCC 12.3
But I failed to build LinuxSampler for the next coming version of my
distribution using GCC15.2 :
my system was not supposed to be UNIX98 compatible
But indeed it is
I simply have had to add this patch to add one line in configure.ac and
it's OK now :
--- /configure.ac 2025-11-07 14:35:24.000000000 +0100
+++ /configure.ac 2025-11-09 19:12:47.608538979 +0100
@@ -131,6 +131,7 @@
#define _GNU_SOURCE 1
#endif
#include <features.h>
+#include <stdlib.h>
void main(void) {
#if _XOPEN_SOURCE >= 500
exit(0); /* UNIX98 compatible */
Maybe it is useful to add this line #include <stdlib.h>
inside your source to be compliant with the next GCC15
Best Regards
|
|
From: Christian S. <sch...@li...> - 2025-11-12 12:14:48
|
On Tuesday, November 11, 2025 12:15:22 AM CET Philippe DIDIER wrote:
[...]
> But I failed to build LinuxSampler for the next coming version of my
> distribution using GCC15.2 :
> my system was not supposed to be UNIX98 compatible
> But indeed it is
>
> I simply have had to add this patch to add one line in configure.ac and
> it's OK now :
>
> --- /configure.ac 2025-11-07 14:35:24.000000000 +0100
> +++ /configure.ac 2025-11-09 19:12:47.608538979 +0100
> @@ -131,6 +131,7 @@
> #define _GNU_SOURCE 1
> #endif
> #include <features.h>
> +#include <stdlib.h>
> void main(void) {
> #if _XOPEN_SOURCE >= 500
> exit(0); /* UNIX98 compatible */
Thanks for letting us know!
Could you provide more details? I assume you are building on Windows, right?
What are the exact compile errors you get?
That Unix98 check is fairly old. So the question is whether we should change
the check here, or something in our sources. Because on Windows you get more
and more POSIX APIs. Back then we simply considered its either UNIX(98) or
Windows.
For instance, chances are that stdlib.h is simply doing #undef _GNU_SOURCE
there, in that case this #include would just fight the symptom.
/Christian
|
|
From: Philippe D. <phi...@la...> - 2025-11-12 18:27:55
|
Le 12/11/2025 à 13:14, Christian Schoenebeck a écrit :
> On Tuesday, November 11, 2025 12:15:22 AM CET Philippe DIDIER wrote:
> [...]
>> But I failed to build LinuxSampler for the next coming version of my
>> distribution using GCC15.2 :
>> my system was not supposed to be UNIX98 compatible
>> But indeed it is
>>
>> I simply have had to add this patch to add one line in configure.ac and
>> it's OK now :
>>
>> --- /configure.ac 2025-11-07 14:35:24.000000000 +0100
>> +++ /configure.ac 2025-11-09 19:12:47.608538979 +0100
>> @@ -131,6 +131,7 @@
>> #define _GNU_SOURCE 1
>> #endif
>> #include <features.h>
>> +#include <stdlib.h>
>> void main(void) {
>> #if _XOPEN_SOURCE >= 500
>> exit(0); /* UNIX98 compatible */
> Thanks for letting us know!
>
> Could you provide more details? I assume you are building on Windows, right?
> What are the exact compile errors you get?
>
> That Unix98 check is fairly old. So the question is whether we should change
> the check here, or something in our sources. Because on Windows you get more
> and more POSIX APIs. Back then we simply considered its either UNIX(98) or
> Windows.
>
> For instance, chances are that stdlib.h is simply doing #undef _GNU_SOURCE
> there, in that case this #include would just fight the symptom.
>
> /Christian
>
>
>
>
> _______________________________________________
> Linuxsampler-devel mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel
Hi Christian
I am using a Linux distribution (Mageia)
The actual version of Mageia is Mageia9
No problem to build LinuxSampler 2.4.1 with GCC 12.3
But we are preparing the next MAgeia10 inside Mageia Caludron
and Mageia10 will be built upon GCC15.2
That's where the problem appeared (GCC15.x is more strict)
The workaround was to modify configure.ac with a patch
adding only :
#include <stdlib.h> after line 133 That's enough
|
|
From: Christian S. <sch...@li...> - 2025-11-23 16:18:30
|
On Wednesday, 12 November 2025 19:27:41 CET Philippe DIDIER wrote:
> Le 12/11/2025 à 13:14, Christian Schoenebeck a écrit :
> > On Tuesday, November 11, 2025 12:15:22 AM CET Philippe DIDIER wrote:
> > [...]
> >
> >> But I failed to build LinuxSampler for the next coming version of my
> >> distribution using GCC15.2 :
> >> my system was not supposed to be UNIX98 compatible
> >> But indeed it is
> >>
> >> I simply have had to add this patch to add one line in configure.ac and
> >> it's OK now :
> >>
> >> --- /configure.ac 2025-11-07 14:35:24.000000000 +0100
> >> +++ /configure.ac 2025-11-09 19:12:47.608538979 +0100
> >> @@ -131,6 +131,7 @@
> >>
> >> #define _GNU_SOURCE 1
> >> #endif
> >> #include <features.h>
> >>
> >> +#include <stdlib.h>
> >>
> >> void main(void) {
> >> #if _XOPEN_SOURCE >= 500
> >> exit(0); /* UNIX98 compatible */
> >
[...]
> I am using a Linux distribution (Mageia)
> The actual version of Mageia is Mageia9
> No problem to build LinuxSampler 2.4.1 with GCC 12.3
>
> But we are preparing the next MAgeia10 inside Mageia Caludron
> and Mageia10 will be built upon GCC15.2
> That's where the problem appeared (GCC15.x is more strict)
> The workaround was to modify configure.ac with a patch
> adding only :
> #include <stdlib.h> after line 133 That's enough
I was able to reproduce this with GCC 14 as well. Apparently not a compiler
version issue. Root cause was the exit() function not been declared.
Apparently stdlib.h was previously included by features.h.
I fixed this now by replacing the exit function calls by a simple return
statement, and also addressed other configure checks that were prone to this
issue as well:
https://svn.linuxsampler.org/cgi-bin/viewvc.cgi?view=revision&revision=4413
Thanks!
/Christian
|
|
From: Jim H. <la...@gm...> - 2025-11-21 16:11:17
|
Is it possible to export the samples from a .gig file to .wav format using GigEdit? Jim |
|
From: Christian S. <sch...@li...> - 2025-11-22 15:30:32
|
On Friday, 21 November 2025 17:11:04 CET Jim Hines wrote: > Is it possible to export the samples from a .gig file to .wav format > using GigEdit? Not with Gigedit ATM (only import/update), but you can use libgig's gigextract command line tool (see 'man gigextract'). /Christian |
|
From: Jim H. <la...@gm...> - 2025-11-22 17:43:00
|
On 11/22/25 10:30 AM, Christian Schoenebeck wrote: > On Friday, 21 November 2025 17:11:04 CET Jim Hines wrote: >> Is it possible to export the samples from a .gig file to .wav format >> using GigEdit? > Not with Gigedit ATM (only import/update), but you can use libgig's gigextract > command line tool (see 'man gigextract'). > > /Christian > > > > > _______________________________________________ > Linuxsampler-devel mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel Yes, thank you. I figured this out about an hour after posting to the list. It works well! Jim |
|
From: Jim H. <la...@gm...> - 2025-11-22 18:03:30
|
Is there any interest in hosting a full suite of RPMs for Fedora 41/42? I have been building them since LinuxSampler 2.4.0. There was one caveat to building linuxsampler. There is a conflict with Fedora package nilfs-utils which also contains a /usr/bin/lscp so I renamed the LS one to linuxsampler-lscp along with its man document. The following RPMs are currently available: gigedit-1.2.3-1.fc41.x86_64.rpm libgig-4.5.1-1.fc41.x86_64.rpm libgig-devel-4.5.1-1.fc41.x86_64.rpm liblscp-1.0.1-1.fc41.x86_64.rpm liblscp-devel-1.0.1-1.fc41.x86_64.rpm linuxsampler-2.4.1-1.fc41.x86_64.rpm linuxsampler-devel-2.4.1-1.fc41.x86_64.rpm qsampler-1.0.1.7git.279c08-2.fc41.x86_64.rpm They may be downloaded from my google drive: https://drive.google.com/drive/folders/1mpZ-bcxL5bdrSKIiOOR71OMvV5t2I0B6?usp=drive_link Jim |