similar to: LDFLAGS of the Makefile

Peter, I am trying to get memdisk to work with grub and have run into a problem. Grub loads memdisk into the 0x9000 segment and then starts it at location 0x90200. I run into problems in the first printf statement. It turns out that printf uses a switch statement that compiles into a jump table. When I reach this jump table, I believe the code is jumping into hyperspace due to the jump table

In an attempt to solve some of the dependency issues when building klibc library I started to do a modular build of klibc library. The priciple is simple. build all sub-directories specified with lib-y := dir/ before the final lib.a But reading "man ar" it was not obvious if: ar cp lib.a dir/lib.a dir2/lib.a file1.o file2.o would produce the desired result. The linux kernel uses lr

Also there are lines as follows: <ppc64> int stat::stat(const char *, struct stat *); Should they be changed likewise too..? I mean to <?> Thanks, Anil On 16 October 2013 13:40, Anil Singhar <anil.singhar at linaro.org> wrote: > OK, I will change all <!aarch64> to <?> then. How about lines declared > like the following: > >

Hello, First of all, thank you for your great work !! There are my (stupid ?) questions : Why loading (kernel and initrd) is so slow ? Is it a limitation beacuse using BIOS's calls ? What can I do to accelerate that ? (if possible of course ...) Once again, thank you very much for your absoluty amazing isolinux ! Best regards, /* ** redseb <redseb at goupilfr.org> **

Hi, I am trying to use MEMDISK from the GRUB boot loader, and gets stuck on the memory detection. MEMDISK reports dos_mem = 0 low_mem = 0 high_mem = 0

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

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

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

On Jun 19, 2008, at 12:01 PM, Rafael Espindola wrote: > <ldflags.patch> Makes sense to me. If you built with and without LDFLAGS enabled should probably just commit it - or do you need someone to commit for you? -eric

> Makes sense to me. If you built with and without LDFLAGS enabled > should probably just commit it - or do you need someone to commit for > you? I can commit it. I was just not sure if this was an intentional difference. I am running a bootstrap without a LDFLAGS. Will commit if it pass. > -eric > _______________________________________________ > LLVM Developers mailing list

> I can commit it. I was just not sure if this was an intentional > difference. I am running a bootstrap without a LDFLAGS. Will commit if > it pass. The bootstrap was OK, but I am getting the following error trying to commit: svn: Commit failed (details follow): svn: MKACTIVITY of '/svn/llvm-project/!svn/act/05b8ac29-8fd9-4f8e-9c3c-d39e89ade19f': 400 Bad Request

On Jun 19, 2008, at 4:04 PM, Rafael Espindola wrote: > The bootstrap was OK, but I am getting the following error trying to > commit: > > svn: Commit failed (details follow): > svn: MKACTIVITY of > '/svn/llvm-project/!svn/act/05b8ac29-8fd9-4f8e-9c3c-d39e89ade19f': 400 > Bad Request (http://llvm.org) > > Any idea what could be wrong? Nope, not really... but

http://bugzilla.mindrot.org/show_bug.cgi?id=1234 Summary: configure adds opensc libs to LDFLAGS when it should use LIBS Product: Portable OpenSSH Version: -current Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: Build system AssignedTo:

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

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 (<=

Pass the LDFLAGS properly as arguments for the C linker when using ocamlmklibs via the -ldopt option. Followup of commit 34c23403c51a4d59d826c8045e06f9aabc2ceb16. --- ocaml/Makefile.am | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ocaml/Makefile.am b/ocaml/Makefile.am index 752fc109c..4d13eed97 100644 --- a/ocaml/Makefile.am +++ b/ocaml/Makefile.am @@ -64,14 +64,14 @@

Full_Name: Denis Sunko Version: 1.3.1 OS: HP-UX 11.0 Submission from: (NULL) (161.53.2.114) I invoked configure by env LDFLAGS=/opt/fortran90/lib ./configure --with-f77=f90 Problem: although configure completed to (its own) satisfaction, the LDFLAGS information was not propagated everywhere; I had to change the line PKG_LIBS = -l:libF90.a -lcl -lisamstub to PKG_LIBS =

Hi, sometimes packages (in this case "pbv") can't be installed on my linux system because in the tarball in src/Makevars there is a line like PKG_LIBS = `$(R_HOME)/bin/Rscript -e "Rcpp:::LdFlags()"` $(LAPACK_LIBS)? The command within the backticks doesn't return anything (i.e, no additional c++ libraries are needed) but because of the backticks an empty argument is