search for: buildflag

On Tue, 21 May 2024 14:48:48 +0200 Kurt Hornik <Kurt.Hornik at wu.ac.at> wrote: > I guess foer the CXXFLAGS we want dpkg-buildflags --get CXXFLAGS? It must be the case. It's both the documented option [1] and it currently differs from CFLAGS in the offending flag: root at 93e09ba5b6fb:/# diff -u <(dpkg-buildflags --get CFLAGS | sed 's/ /\n/g') <(dpkg-buildflags --get CXXFLAGS | sed 's/ /\n/g') --- /...

...t debian.org> wrote: >> You cannot undo what it is in R's own /etc/R/Makeconf via a >> programmatic way via some sort of option or alike. > I think this is about the following line in debian/rules: Without having looked in much detail, I guess foer the CXXFLAGS we want dpkg-buildflags --get CXXFLAGS? Best -k > optimflags = `DEB_BUILD_MAINT_OPTIONS=optimize=-lto dpkg-buildflags --get CFLAGS` > https://sources.debian.org/src/r-base/4.4.0-2/debian/rules/#L101 > ...which later propagares to cxxflags = $(optimflags) and > eventually CXXFLAGS="$(cxxflags)&qu...

...Dirk Eddelbuettel <edd at debian.org> wrote: > You cannot undo what it is in R's own /etc/R/Makeconf via a > programmatic way via some sort of option or alike. I think this is about the following line in debian/rules: optimflags = `DEB_BUILD_MAINT_OPTIONS=optimize=-lto dpkg-buildflags --get CFLAGS` https://sources.debian.org/src/r-base/4.4.0-2/debian/rules/#L101 ...which later propagares to cxxflags = $(optimflags) and eventually CXXFLAGS="$(cxxflags)" ... ./configure. On Sid, dpkg-buildflags --get CFLAGS includes -Werror=implicit-function-declaration, which g++ do...

...SIONS=5 debian/rules maint debuild -e PHP_VERSIONS=5 -us -uc cd .. sudo dpkg -i php5-xapian_*.deb Though, it is failing with this error message: dpkg-buildpackage -rfakeroot -D -us -uc dpkg-buildpackage: warning: using a gain-root-command while being root dpkg-buildpackage: export CFLAGS from dpkg-buildflags (origin: vendor): -g -O2 dpkg-buildpackage: export CPPFLAGS from dpkg-buildflags (origin: vendor): dpkg-buildpackage: export CXXFLAGS from dpkg-buildflags (origin: vendor): -g -O2 dpkg-buildpackage: export FFLAGS from dpkg-buildflags (origin: vendor): -g -O2 dpkg-buildpackage: export LDFLAGS from...

...cks the use of fortified libc N: functions. Either there are no potentially unfortified functions called N: by any routines, all unfortified calls have already been fully validated N: at compile-time, or the package was not built with the default Debian N: compiler flags defined by dpkg-buildflags. If built using N: dpkg-buildflags directly, be sure to import CPPFLAGS. N: N: NB: Due to false-positives, Lintian ignores some unprotected functions N: (e.g. memcpy). N: N: Refer to https://wiki.debian.org/Hardening and N: https://bugs.debian.org/673112 for details. N:...

With the latest gitwine, beginning with wine 1.3.35, I can't run any of my games anymore. Every game I tested crashes with the following backtrace somewhere in its logs : =>0 0x7c58c255 DSOUND_RecalcVolPan+0xa5(volpan=0x67d3068) [/wine-git/dlls/dsound/mixer.c:58] in dsound (0x0032f194) 1 0x7c57b463 IDirectSoundBufferImpl_Create+0x382(device=0x67d2848, pdsb=0x32f2a8, dsbd=0x32f360)

...=> lib/clang/libllvmx86instprinter (all) ===> lib/clang/libllvmx86utils (all) ===> lib/clang/include (all) 1 error *** [everything] Error code 2 1 error *** [buildworld] Error code 2 Stop in /asp/src. My source is in /asp/src (symlinked from /usr/src also). clang is set in /usr/local/etc/buildflags.conf. I have disabled ccache while I try and work through this error - so it is not a factor. -- View this message in context: http://freebsd.1045724.n5.nabble.com/buildworld-with-clang-breaks-because-no-cc-tp5763472.html Sent from the freebsd-stable mailing list archive at Nabble.com.

...fied libc > N: functions. Either there are no potentially unfortified functions called > N: by any routines, all unfortified calls have already been fully validated > N: at compile-time, or the package was not built with the default Debian > N: compiler flags defined by dpkg-buildflags. If built using > N: dpkg-buildflags directly, be sure to import CPPFLAGS. > N: > N: NB: Due to false-positives, Lintian ignores some unprotected functions > N: (e.g. memcpy). > N: > N: Refer to https://wiki.debian.org/Hardening and > N: https://bugs.deb...

On 21 May 2024 at 13:01, Jeroen Ooms wrote: | Compiling packages with C++ code using the default r-base-dev | configuration on debian:sid shows a lot of: | | cc1plus: warning: '-Werror=' argument | '-Werror=implicit-function-declaration' is not valid for C++ | | Can this flag be removed from R CMD config CXXFLAGS? "No." That was quoting Simon Urbanek from a few

...---------------------------------------------------------- @@ -65,15 +62,10 @@ AFLAGS := $(CFLAGS) -D__ASSEMBLY__ $(obj)/bzImage: IMAGE_OFFSET := 0x100000 $(obj)/bzImage: EXTRA_CFLAGS := -D__BIG_KERNEL__ $(obj)/bzImage: EXTRA_AFLAGS := $(SVGA_MODE) $(RAMDISK) -D__BIG_KERNEL__ -$(obj)/bzImage: BUILDFLAGS := -b -quiet_cmd_image = BUILD $@ -cmd_image = $(obj)/tools/build $(BUILDFLAGS) $(obj)/setup.bin \ - $(obj)/vmlinux.bin $(ROOT_DEV) > $@ +all: $(obj)/bzImage -$(obj)/zImage $(obj)/bzImage: $(obj)/setup.bin \ - $(obj)/vmlinux.bin $(obj)/tools/build FORCE - $(call if_changed,i...

...---------------------------------------------------------- @@ -65,15 +62,10 @@ AFLAGS := $(CFLAGS) -D__ASSEMBLY__ $(obj)/bzImage: IMAGE_OFFSET := 0x100000 $(obj)/bzImage: EXTRA_CFLAGS := -D__BIG_KERNEL__ $(obj)/bzImage: EXTRA_AFLAGS := $(SVGA_MODE) $(RAMDISK) -D__BIG_KERNEL__ -$(obj)/bzImage: BUILDFLAGS := -b -quiet_cmd_image = BUILD $@ -cmd_image = $(obj)/tools/build $(BUILDFLAGS) $(obj)/setup.bin \ - $(obj)/vmlinux.bin $(ROOT_DEV) > $@ +all: $(obj)/bzImage -$(obj)/zImage $(obj)/bzImage: $(obj)/setup.bin \ - $(obj)/vmlinux.bin $(obj)/tools/build FORCE - $(call if_changed,i...

...---------------------------------------------------------- @@ -65,15 +62,10 @@ AFLAGS := $(CFLAGS) -D__ASSEMBLY__ $(obj)/bzImage: IMAGE_OFFSET := 0x100000 $(obj)/bzImage: EXTRA_CFLAGS := -D__BIG_KERNEL__ $(obj)/bzImage: EXTRA_AFLAGS := $(SVGA_MODE) $(RAMDISK) -D__BIG_KERNEL__ -$(obj)/bzImage: BUILDFLAGS := -b -quiet_cmd_image = BUILD $@ -cmd_image = $(obj)/tools/build $(BUILDFLAGS) $(obj)/setup.bin \ - $(obj)/vmlinux.bin $(ROOT_DEV) > $@ +all: $(obj)/bzImage -$(obj)/zImage $(obj)/bzImage: $(obj)/setup.bin \ - $(obj)/vmlinux.bin $(obj)/tools/build FORCE - $(call if_changed,i...

...---------------------------------------------------------- @@ -65,15 +62,10 @@ AFLAGS := $(CFLAGS) -D__ASSEMBLY__ $(obj)/bzImage: IMAGE_OFFSET := 0x100000 $(obj)/bzImage: EXTRA_CFLAGS := -D__BIG_KERNEL__ $(obj)/bzImage: EXTRA_AFLAGS := $(SVGA_MODE) $(RAMDISK) -D__BIG_KERNEL__ -$(obj)/bzImage: BUILDFLAGS := -b -quiet_cmd_image = BUILD $@ -cmd_image = $(obj)/tools/build $(BUILDFLAGS) $(obj)/setup.bin \ - $(obj)/vmlinux.bin $(ROOT_DEV) > $@ +all: $(obj)/bzImage -$(obj)/zImage $(obj)/bzImage: $(obj)/setup.bin \ - $(obj)/vmlinux.bin $(obj)/tools/build FORCE - $(call if_changed,i...

https://dovecot.org/releases/2.2/rc/dovecot-2.2.32.rc1.tar.gz https://dovecot.org/releases/2.2/rc/dovecot-2.2.32.rc1.tar.gz.sig There are various changes in this release that can be used to significantly reduce disk IO with: 1) NFS storage especially, but I guess also other remote filesystems and even some with local disks 2) When mail storage and INDEX storage are separated * imapc: Info-level

https://dovecot.org/releases/2.2/rc/dovecot-2.2.32.rc1.tar.gz https://dovecot.org/releases/2.2/rc/dovecot-2.2.32.rc1.tar.gz.sig There are various changes in this release that can be used to significantly reduce disk IO with: 1) NFS storage especially, but I guess also other remote filesystems and even some with local disks 2) When mail storage and INDEX storage are separated * imapc: Info-level

Initially out there as #965245. I strongly prefer to build ARM64 packages on non-ARM systems. Something about my main build machine having twice the cores and twice the clock speed. As such after many builds I've managed to generate a set of patches which appear to mostly function to get functioning cross-builds of Xen. These are NOT a 100% solution. Some packaging hacks were needed. In

This series: 1. Updates the boot protocol to version 2.07 2. Clean up the existing build process, to get rid of tools/build and make the linker do more heavy lifting 3. Make the bzImage payload an ELF file. The bootloader can extract this as a naked ELF file by skipping over boot_params.setup_sects worth of 16-bit setup code. 4. Update the boot_params to 2.07, and update the

This series: 1. Updates the boot protocol to version 2.07 2. Clean up the existing build process, to get rid of tools/build and make the linker do more heavy lifting 3. Make the bzImage payload an ELF file. The bootloader can extract this as a naked ELF file by skipping over boot_params.setup_sects worth of 16-bit setup code. 4. Update the boot_params to 2.07, and update the

Right that I had completely missed, I have added the files and verified that it builds with CMake from the tar on Linux (out of the git repo) I am parsing the package_version file from the tarball if it exists so it should maintain the version info. //Marcus ________________________________ From: Jean-Marc Valin <jmvalin at jmvalin.ca> Sent: Tuesday, April 2, 2019 11:38 To: Marcus

...s 2016-05-07 13:19:27.000000000 +0200 +++ samba-4.4.3+dfsg/debian/rules 2016-05-26 17:00:53.689073733 +0200 @@ -69,7 +69,7 @@ --enable-selftest %: - dh $* --with python2 --with systemd + dh $* --with python2 override_dh_auto_configure: $(shell dpkg-buildflags --export=configure) $(WAF) configure \ @@ -97,9 +97,6 @@ @echo "** tests disabled" endif -override_dh_systemd_start: - dh_systemd_start -pctdb --no-start --no-restart-on-upgrade - override_dh_installdocs-arch: cp ctdb/config/events.d/README ctdb/README.events...