similar to: [PATCH] build: Pass CFLAGS & LDFLAGS to final supermin link (RHBZ#1624175).

On Friday, 31 August 2018 10:03:31 CEST Richard W.M. Jones wrote: > We also use -runtime-variant _pic which selects the OCaml runtime > linked with -fPIC. This will cause a performance regression on i686 > although that probably doesn't matter now. This is for supermin, right? > A bigger issue is that it will stop supermin from building with older > versions of OCaml (<=

On 8/18/20 5:50 AM, Richard W.M. Jones wrote: > --- > +++ b/configure.ac > @@ -457,11 +457,13 @@ AS_CASE([$host_os], > [mingw*|msys*|cygwin*], [ > is_windows=yes > NO_UNDEFINED_ON_WINDOWS="-no-undefined" > + LINK_LIBNBDKIT_ON_WINDOWS='$(top_builddir)/server/libnbdkit.la' Cygwin supports linking with undefined symbols, but it

Hello I am trying to install supermin on debian 10 (buster) and I am getting the following error: checking /usr/sbin/mke2fs -t or -T... -t checking for EXT2FS... no configure: error: in `/root/supermin-5.1.16': configure: error: The pkg-config script could not be found or is too old. Make sure it is in your PATH or set the PKG_CONFIG environment variable to the full path to pkg-config.

--- configure.ac | 2 ++ filters/blocksize/Makefile.am | 1 + filters/cache/Makefile.am | 1 + filters/cacheextents/Makefile.am | 1 + filters/cow/Makefile.am | 1 + filters/ddrescue/Makefile.am | 1 + filters/delay/Makefile.am | 3 +++ filters/error/Makefile.am | 1 + filters/exitlast/Makefile.am | 3 +++

OCaml has a small runtime which is statically linked into the virt tools (providing things like GC and primitives). Since OCaml 4.03 it has been possible to select variants of this runtime, one of which is compiled with -fPIC, using ‘ocamlopt -runtime-variant _pic’. This has performance implications on i686, but is relatively free on other architectures. Since it (in theory) adds to the

Hi all, There is a discussion going on one russian forum about NUT cross-compiling and packaging for some custom embedded firmware. And one of the authors complained about NUT script for checking ssl library ignoring supplied CFLAGS and LDFLAGS with the desired include and library paths. I checked several scripts in m4 folder and all of them do something like this:

Hi Alexander, no, I am not responsible for this! It's true that I created the scripts in m4/, but I only copied what was previously in configure.in. Try: svn up -r2 configure.in and you'll see that the code in question has been there since the beginning of SVN time (line 175). I cannot say why it was done that way. Probably because nobody needed a more general mechanism. Using

Split CFLAGS into CFLAGS (user part) and AM_CFLAGS (not-so-user part; variable name taken from automake, but otherwise no relation). Also add LDFLAGS. This allows me to use `make CFLAGS="-O2 -fPIE" LDFLAGS="-pie"` without dropping the other important (AM_CFLAGS) flags. Signed-off-by: Jan Engelhardt <jengelh@computergmbh.de> --- btrfs-progs/Makefile | 17

Use the ocamlmklib -ldopt flag to pass the general $(LDFLAGS) when calling gcc to link dllmlhivex.so. We were already passing $(CFLAGS) when building the object file. When building using Fedora's standard hardening flags this gives: ocamlmklib -o mlhivex hivex_c.o hivex.cmo \ -verbose -ldopt '-Wl,-z,relro -specs=/usr/lib/rpm/redhat/redhat-hardened-ld' \ -L../lib/.libs

I notice that the user is not able to set their own CFLAGS or LDFLAGS in the ao, ogg, vorbis, and voribs-tools projects. Is there a reason for this? I understand the fact that these modules want to set extremely high optimization flags, and that most users won't know what these are offhand, but there are times when it is useful for the user to specify their own CFLAGS/LDFLAGS. For example,

Hi, this work makes supermin use the rpm library instead of invoking rpm directly. This, together with a needed refactoring of the dependency resolution, should help in make supermin faster on rpm-based systems. Surely the patches will still need polishing, especially for behaviours of newly added stuff, but at least it's a good starting point. Noting that you need rpm-devel on most of rpm

Hi Folks - I''m pretty new to ACPI (don''t know my ASL from a hole in the ground :-), but I think the _PRT method has the PIC/APIC cases reversed. I''m looking at tools/firmware/acpi/acpi_dsdt.asl. The ACPI spec says a _PIC method (if defined) will be called with an argument of 1 if the host is using APIC interrupts. If the host is using PIC interrupts instead, it

Hello, i want to install ocfs2-tools-1.2.0-1 on slackware 10.2 (up-to-date) with 2.6.17.2 kernel and i got error: ./configure checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no

Hello, i want to install ocfs2-tools-1.2.0-1 on slackware 10.2 (up-to-date) with 2.6.17.2 kernel and i got error: ./configure checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no

There is a small test provided. I tested this a lot more locally and it seems pretty robust. Rich.

'make distcheck' calls us out for leaving files behind after 'make distclean' that were not present in the tarball. Either these files are expensive enough that end users should not be required to regenerate them (so they should be distributed), or they should be cleaned when a user asks to get back to the pristine tarball state. Automake suggests this hierarchy of cleaning:

The ocaml.opt compiler defaults to building things in the same directory as its input; we need explicit -o options to build in a VPATH $(builddir) when $(srcdir) is read-only (as is the case during 'make distcheck'). We also have to build any side effect files explicitly in cases where we can't directly use -o to control those outputs alongside the final product. Thanks: Richard W.M.

On my Gentoo box I updated openssl to openssl-1.0.0a-r3 I'm not able to compile with openssl-1.0.0a-r3 if I want a static binary ./configure LDFLAGS=-static the configure scripts complains like this: checking for RAND_pseudo_bytes... no configure: error: Missing OpenSSL functionality, make sure you have installed the latest version. this was working with previous version of OpenSSL.

Hi, If say ppc where LDFLAGS=, you get the problem that klcc is generated like: ----- @LDFLAGS = ( '' ) ----- which then causes '' to get passed to ld, which gives: ----- /usr/bin/ld: : No such file: No such file or directory ----- One of two ways (I tried over here at least) to fix it, namely the quick hack: ----- --- 1/makeklcc.pl 2005-03-10 00:22:03.000000000 +0200

The attached patch permits setting the LDFLAGS variable in the call to configure. This is the behavior of configure on gcc trunk. Not sure why llvm-gcc is different. This is necessary for building llvm-gcc in cases where some libraries are in strange places: CPPFLAGS="-I/foo/include" LDFLAGS="-L/foo/lib" configure .... Cheers, -- Rafael Avila de Espindola Google Ireland