search for: ld_flags

...tps://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=f6aec96dce1ddbd8961a3aa8a2925db2021719bb). Building syslinux EFI images with this -zseparate-code enabled creates broken EFI images, since efi/wrapper.c only copies the first PT_LOAD segment to the EFI. This patch adds -znoseparate-code to the LD_FLAGS for EFI builds to restore the original behavior. PS: I am aware that development activity is low. We still wanted to contribute this fix in case it may be helpful to anyone. Thanks Johannes Signed-off-by: Johannes Frohnhofen <jf at daedalean.ai> --- mk/efi.mk.orig 2020-07-28 12:31:48.8143...

Everyone, I would like to build the LLVM toolchain and the GCC front end as statically linked executables, but I do not see a configure option to set this. A quick check of the FAQ and build documents comes up empty. Is there a linker switch setting or environment variable for the Makefile? Dave Koogler

On Tuesday 29 April 2008 14:52:49 David J.A. Koogler wrote: > Everyone, > > I would like to build the LLVM toolchain and the GCC front end as > statically linked executables, but I do not see a configure > option to set this. A quick check of the FAQ and build documents > comes up empty. Is there a linker switch setting or environment > variable for the Makefile? > >

...cally linked tools. Kenneth Boyd wrote: > The --disable-shared option to configure should work (like it does for > most configure-scripted projects). No, I tried that and still got dynamically linked tools. It did not work for GCC either. I got the GCC tools statically linked by defining LD_FLAGS on the make invocation: make LD_FLAGS = \"-static\" Searching through the LLVM makefiles, I saw a make variable called LD.Flags but alas trying to set that externally like I did for GCC did not have the desired affect. All of the tools were still linked dynamically. So at least I...

...\ --configure-args='--with-gl-includes=/usr/X11/include/NVIDIA --with-gl-libs=/usr/X11/lib/NVIDIA/amd64' $TMPBUILD And thus configure tries: cc ... -lGL -L/usr/X11/lib/NVIDIA/amd64 which obviously fails: the path needs to be placed before -l... So the correct way is to add the path to LD_FLAGS instead of LIBS. To get the path at the correct place into the to PKG_LIBS limitted Makevars, one needs to add the path, when the LIB expansion has been done. Suggested patch: --- rgl/configure.ac.orig Mon Feb 2 14:31:24 2009 +++ rgl/configure.ac Tue Jan 12 06:16:52 2010 @@ -157,9 +157,12 @...

GNU ld supports most long options with either one or two dashes. For compatibility, lld has to support both. For newer and lld specific options, we don't have such compatibility problem. I'd suggest we reject one-dash long options to avoid collision with short options. For example, * -lto-emit-obj can be read as -l to-emit-obj * -thinlto-cache-dir= means -t -h inlto-cache-dir= in GNU

Hello, We have just migrated a server from sun solaris 8 to sun solaris 10. In the old machine we had a Samba 3.0.20b and in the new one, we have samba 3.0.21, both compiled like this with no problems: env LD_FLAGS="-L/usr/local/lib" ./configure --with-ldapsam --without-pam --with-quotas --with-ldap --with-included-popt --with-acl-support --with-libsmbclient We share user's homes by default working correctly. All this works correctly in the old machine with Solaris 8, but in the new one with...

...ure --with-tcl-config=/usr/lib/tcl8.5/tclConfig.sh --with-tk-config=/usr/lib/tk8.5/tkConfig.sh CFLAGS="-fsanitize=address -fsanitize=undefined -fno-sanitize=float-divide-by-zero,vptr " CXXFLAGS="-fsanitize=address -fsanitize=undefined -fno-sanitize=float-divide-by-zero,vptr " LD_FLAGS="-pthread -fopenmp-lclang_rt.asan_cxx-x86_64 -fopenmp=libgomp" CC="clang-3.8 -fsanitize=address -fsanitize=undefined -fno-sanitize=float-divide-by-zero,vptr" CXX="clang++-3.8 -fsanitize=address -fsanitize=undefined -fno-sanitize=float-divide-by-zero,vptr" ## I get i...

...n function `dlfcn_bind_func': dso_dlfcn.o(.text+0x309): undefined reference to `dlsym' collect2: ld returned 1 exit status make: *** [ssh] Error 1 error: Bad exit status from /var/tmp/rpm-tmp.46927 (%build) ---------------------------------- I do not know why configure does not add -ldl to LD_FLAGS, I _have_ installed glibc-devel, and ----------------------- ls -l /lib/libdl* /usr/lib/libdl* -rwxr-xr-x 1 root root 11728 Jun 18 16:13 /lib/libdl-2.2.5.so lrwxrwxrwx 1 root root 14 Jun 27 13:54 /lib/libdl.so.2 -> libdl-2.2.5.so -rw-r--r-- 1 root root...

Hi all, In order to get icecast working i found that i had to install libao-0.8.4 libogg-1.1 libvorbis-1.0.1 flac-1.1.0 speex-1.0.3 vorbistools-1.0.1 icecast-2.0.0 So i grapped the source files. I copied all the files to an 32-bit Intel machine, and *there* all files configured, compiled and installed OK But on the intended target machine (SUN blade server) i have a problem... libao and libogg

Here's a patch series to make libguestfs use gnulib via a git submodule. The first thing I did was to look at the failures from "make syntax-check" and fix the config.h-related ones below. The others are now temporarily disabled via a variable in cfg.mk. I fixed the config-h problems and moved those change sets to precede the test-adding one, so that bisection still works, even if

...ier-orchard.blogspot.com/2013/11/raspberry-pixf86-video-fbdev.html It's not in English, but you get can get the general idea of how to move along. Also, tripplite_usb failed to build for me with a bunch of undefined errors. I was able to fix it by editing the Makefile and adding -lusb to the LD_FLAGS. So - here I am starting up nut in debugging level 5, and it looks "promising"? :-) =~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2014.06.28 21:54:46 =~=~=~=~=~=~=~=~=~=~=~= ]0;pi at raspberrypi: ~/nut[01;32mpi at raspberrypi [01;34m~/nut $ sudo ./drivers/tripplite_usb -u root -a SMART500RT1U -D...

I'm trying to get R 1.9.0 running on AIX 5.1 with the standard AIX compilers (xlc, xlf) and it is failing 2 of the tests, test-Reg in reg-tests-1.R like this: bash-2.05b$ tail -30 reg-tests-1.Rout.fail [,1] [,2] [1,] 1 3 [2,] 2 4 [3,] 1 3 [4,] 2 4 > stopifnot(typeof(res) == "list") > ## were not implemented in 1.8.1 > > > ## Date objects with

This patchset is for more paravirtualization on ia64/pv_ops. - paravirtualize fsys call (fsys.S) by multi compile - paravirtualize gate page (gate.S) by multi compile - support save/restore For this purpose, the followings needs to be paravirtualized - ar.itc instruction - sched_clock() This is because timer may changed before/after saving/restoring. For convenience the working full

This patchset is for more paravirtualization on ia64/pv_ops. - paravirtualize fsys call (fsys.S) by multi compile - paravirtualize gate page (gate.S) by multi compile - support save/restore For this purpose, the followings needs to be paravirtualized - ar.itc instruction - sched_clock() This is because timer may changed before/after saving/restoring. For convenience the working full

This patchset is for more paravirtualization on ia64/xen domU. - paravirtualize fsys call (fsys.S) by multi compile - paravirtualize gate page (gate.S) by multi compile - support save/restore For this purpose, the followings needs to be paravirtualized - ar.itc instruction - sched_clock() This is because timer may changed before/after saving/restoring. For convenience the working full

This patchset is for more paravirtualization on ia64/xen domU. - paravirtualize fsys call (fsys.S) by multi compile - paravirtualize gate page (gate.S) by multi compile - support save/restore For this purpose, the followings needs to be paravirtualized - ar.itc instruction - sched_clock() This is because timer may changed before/after saving/restoring. For convenience the working full

This patch set is for the next merge window. They are just enhancements of the already merged patches or ia64 porting from x86 paravirt techniques and that their quality is enough for merge. This patch set is for more paravirtualization on ia64/xen domU. This patch set does - remove existing warnings - paravirtualize fsys call (fsys.S) by multi compile - paravirtualize gate page (gate.S) by multi

This patch set is for the next merge window. They are just enhancements of the already merged patches or ia64 porting from x86 paravirt techniques and that their quality is enough for merge. This patch set is for more paravirtualization on ia64/xen domU. This patch set does - remove existing warnings - paravirtualize fsys call (fsys.S) by multi compile - paravirtualize gate page (gate.S) by multi

This patch set is intended for the next merge window. They are just enhancements of the already merged patches or ia64 porting from x86 paravirt techniques and that their quality is enough for merge. This patch set is for more paravirtualization on ia64/xen domU. This patch set does - remove existing warnings - paravirtualize fsys call (fsys.S) by multi compile - paravirtualize gate page (gate.S)