May be related that https://gitlab.freedesktop.org/xorg/lib/libxaw/-/commit/d0fcbd9722ad691ca0b5873c98e8e9c236fa718b changed the definition of XawListChange in <X11/Xaw/List.h> from _Xconst char * to String *, where String is defined as const if _CONST_X_STRINGis defined.
May be related that https://gitlab.freedesktop.org/xorg/lib/libxaw/-/commit/d0fcbd9722ad691ca0b5873c98e8e9c236fa718b changed the definition of XawListChange in <x11 xaw="" list.h=""> from _Xconst char * to String *, where String is defined as const if _CONST_X_STRINGis defined.</x11>
Got almost the same error with the patch in your comment. https://paste.gentoo.zip/oALV47cL I think the issue is that on your system, _Xconst is not properly defined to const like it should be. I've to check why this might be the case.
I think there is a problem here... Applying your patch simply re-introduces 4 incompatible-pointer-types warning (or errors depending on gcc options). I think the issue is that on your system, _Xconst is not properly defined to const like it should be. This is a problem with your X11 configuration and the ancient NAS code. On my Ubuntu 22.04 system (and others) _Xconst is properly defined as const - while on your system it is not for some reason. I've made a patch that I hope will work on your system...
I think there is a problem here... Applying your patch simply re-introduces 4 incompatible-pointer-types warning (or errors depending on gcc options). I think the issue is that on your system, _Xconst is not properly defined to const like it should be. This is a problem with your X11 configuration and the ancient NAS code. On my Ubuntu 22.04 system (and others) _Xconst is properly defined as const - while on your system it is not for some reason. I've made a patch that I hope will work on your system....
Commit e792e4 breaks build with GCC 14 and 15
Fails to build with libXaw-1.0.16
Well my problem was that it was asking for an m4 file that doesn't exist. I didn't expect the original patch to update configure -- just that the project maintainers should be ensuring they dont get out of sync.
I excluded that generated file because it's content depends on third-party files the committer has in his system. Not being the maintainer, I cannot replicate that environment and the patch would be too big, obtrusive, and unhelpful. That means it's maintainer task to regenerate that file. Or, ideally, remove it from git repository. You should be able to generate that file with a command like "autoreconf -i -f config", after installing automake, autoconf, libtool, and maybe other utilities.
The patch modifies configure.ac, but configure is not regenerated and really should be. (It currently does fail with an autoconf error: /usr/bin/m4:aclocal.m4:6178: cannot openacinclude.m4': No such file or directory`.)
Also while testing this with make -k I got a highly confusing error because somehow make succeeded instead of failing??? Even though a rule failed to compile. As a result my build script continued on to the install phase and compiled the failing program without any CFLAGS or LDFLAGS, which "worked" but should not have. It would be ideal if CFLAGS / LDFLAGS defined when the build is configured would persist across invocations... GNU autotools or meson would both do so. (imake is deprecated; xorg uses...
Build fails with LTO
Correct pointer types for GCC 14
Thanks for the patch, I've merged it to master.
Correct pointer types for GCC 14
Correct pointer types for GCC 14
Will fail to build with GCC 13 or 14 because of implicit ints and function declarations
Thanks for merging it. You can close this ticket.
libaudio.so.2.4 is linked without EXTRA_LDOPTIONS linker flags
Sorry for letting this one slip through the cracks. I've applied this to current master. Thanks!
Pass extra linker flags to shared libraries
libaudio.so.2.4 is linked without EXTRA_LDOPTIONS linker flags
Thanks for this patch. I've merged it to master. As for ErrorF, perhaps that can be replaced by osLogMsg() which is used by the server - maybe that can be generalized and used for both client and server.
No implicit ints and function declarations
Will fail to build with GCC 13 or 14 because of implicit ints and function declarations
Release version 1.9.5
config/configure fails because of half-unsetting flags
Hi, I've applied your patch and pushed it to master, thanks! I should have been a little more specific in my commits when I made that change almost 20 years ago, but I've gotten better, I swear! :) At any rate, IIRC the reason I unset CFLAGS was to avoid corruption of the configure run, since that flag would be set by imake and I recall there were build problems with that at the time (with it set).
Unset LDFLAGS for config/configure
config/configure fails because of half-unsetting flags
potential buffer overflow in auphone.c
Fixed in current master.
dia: fix up some compiler warnings
Bump revision to 1.9.4a
auphone: use snprintf to avoid potential buffer overflow
potential buffer overflow in auphone.c
Fails to build with GCC 10
According to the lex & yacc and flex & bison books, using extern FILE *yyin is correct. Obviously, omitting extern worked since introducing the functionality in the year 2000. It still works with GCC versions less than 10. I have tested the patch on Ubuntu 18.04.3 LTS with gcc (Ubuntu 7.4.0-1ubuntu1~18.04.1) 7.4.0. The NAS server builds and parses the configuration with and without extern. Note that using extern FILE *yyin can only be used with a non-reentrant scanner. The scanner used for parsing...
No License file
Closing this bug since the license is included in the README since "forever."
Fix building with GCC 10
Hello Petr, On Thu, Jan 23, 2020 at 12:52:54PM -0000, Petr Písař wrote: [bugs:#7] Fails to build with GCC 10 Status: open Group: v1.0 (example) Created: Thu Jan 23, 2020 12:52 PM UTC by Petr Písař Last Updated: Thu Jan 23, 2020 12:52 PM UTC Owner: nobody Attachments: nas-1.9.4-Fix-building-with-GCC-10.patch (1.5 kB; application/octet-stream) nas-1.9.4 fails to build with GCC 10 due to a double global variable definition. An attached patch fixes it. Thanks for the patch. At first glance it seems sensible,...
Fails to build with GCC 10
AuErrDes.c:177]: (error) Resource leak: fp
Fixed with 81b5b96.
Add a .gitignore file
AuErrDes.c: fclose file on return, fixes bug #6
AuErrDes.c:177]: (error) Resource leak: fp
On a uClibc system, the macro definitions of ab...
Main_Page
Home
Downloading
Downloading
Main_Page
Home
Main_Page
Main_Page
Frequent random crashes on FreeBSD