---- On Fri, 09 May 2025 05:24:20 -0700 Hilmar Preuße <hill...@web.de> wrote ---
On 07.05.25 05:29, Golf Team wrote: Hello, > -std=gnu99 was used when we transitioned from a pure C language > framework to Golf (which is still a C framework, but it's now also > its own language). It just stayed even after we fixed the issues.> > > -std=gnu99 is now removed. > > I installed gcc 15 from debian experimental and fixed the issues. > Golf now compiles and test cleanly. Of course, it does so still for > previous gcc version. > I can confirm that the issue has been solved. I did not test the package itself, i.e. the functionality it promises to provide. Your upstreams Makefile looks very Debian'ish. I guess there are better ways to install only specific file in a Debian package then checking for "we build a Debian package" in the upstream Makefile. But this can be delayed to the time past first upload. I'm thinking about pushing your package to the NEW queue, be informed that it won't be in Debian trixie, so there is no need to hurry. H. -- Testmail Hi Hilmar, thanks for that. I presume you're referring to the GG_DEBIAN_BUILD variable in Makefile, which is used only to guard against including files (or to guard against specific actions) for Debian. It's not used to include anything specific for Debian or to do anything specific for it. It accounts for differences between Debian and other distros (RPM based, such as Fedora or OpenSUSE, or Arch Linux), which need additional files and/or actions. Those additional tasks are currently 1) installing LICENSE file 2) man pages, 3) as well as .dbg files produced by objcopy to make a debug build for Arch package. Those tasks are done for Debian through debian/* files and/or automatically by the build process, so they are excluded from being done through Makefile. Best, Sergio
