similar to: linking external library into module

Thank you, that clears everything up. > -------- Original Message -------- > Subject: RE: [syslinux] linking external library into module > From: "H. Peter Anvin" <hpa at zytor.com> > Date: Thu, September 29, 2016 2:55 pm > To: jeff.williams at pideso.com, syslinux at zytor.com > > > On September 29, 2016 7:16:19 AM PDT, jeff.williams at pideso.com wrote:

I guess there were no dendrites to tickle. I did come up with a partial answer, although why exactly these items are required is still somewhat of a mystery to me. I'll probably investigate further at some point to see about getting a full answer, but here's what I came up with so far. So, in case anyone else is giving this a try: 1) It appears that external libraries will not link

From: Matt Fleming <matt.fleming at linux.intel.com> This series includes a patch (PATCH 1/6) that I sent previously but I thought it was worth sending it again since the rest of the series depends on it, and it also gives a bit of context. These cleanups make it simpler to do the big switchover to ELF modules on the elflink branch because the libraries in $LIBS are now contained in one

From: Matt Fleming <matt.fleming at intel.com> The first two patches in this series are fixes for bugs reported by someone in #syslinux. The third makes dmitest.c32 actually wait for user input. If no one has any objections/concerns, I'll pull this into the official elflink branch. Matt Fleming (3): core: Print error message if we don't load ldlinux.c32 Clean up $(GPLLIB) leak

I'm seeing some sporadic build failures with 'make -j4'. The failures are: make[4]: *** No rule to make target 'hello.c32', needed by 'all'. Stop. I've only seen the failures with com32/samples/hello.c32 and com32/rosh/rosh.c32. I'm not a make expert, but I think it's due to missing dependencies. This patch seems to fix my failures, but I'm

From: Matt Fleming <matt.fleming at linux.intel.com> This series fixes some bugs and switches the elflink branch to be entirely ELF modules. It applies on top of, http://syslinux.zytor.com/archives/2011-April/016369.html The deletions in the diff stat below are mainly from deleting com32/elflink/modules (finally!). Now there should be no duplicate code because we don't need COM32 and

From: Matt Fleming <matt.fleming at intel.com> The following patch series is available at, git://git.zytor.com/users/mfleming/syslinux.git elflink All patches are against the 'elflink' branch. This series fixes a few serious bugs and some behavioural incompatibilities with the 4.x series. Matt Fleming (19): ldlinux: Initialise 'p' before using it. ldlinux: Parse

On Wed, 2019-02-06 at 11:34 -0800, H. Peter Anvin wrote: > On 2/6/19 9:17 AM, Joakim Tjernlund via Syslinux wrote: > > On Wed, 2019-02-06 at 16:00 +0100, Joakim Tjernlund wrote: > > > On Tue, 2019-02-05 at 14:07 -0800, H. Peter Anvin via Syslinux wrote: > > > > CAUTION: This email originated from outside of the organization. Do not click links or open attachments

On Wed, 2019-02-06 at 11:56 -0800, H. Peter Anvin wrote: > CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. > > > On 2/6/19 11:44 AM, Joakim Tjernlund wrote: > > On Wed, 2019-02-06 at 11:34 -0800, H. Peter Anvin wrote: > > > > Great, that tree now

This just came up on IRC, 15:01 < chithead> the first one that fails is ld -m elf_i386 -Wl,-O1 -Wl,--as-needed -Bsymbolic -pie -E --hash-style=gnu -T /var/tmp/portage/sys-boot/syslinux-6.01_pre5/work/syslinux-6.01-pre5/core/i386/syslinux.ld -M -o ldlinux.elf ldlinux.o \ 15:01 < chithead> --start-group libcom32.a --whole-archive

Hi Peter, Please pull the following changes. Paulo, I had to revert your "pxe: resolve names via DNS from protected-mode code" change because dns_resolv() is only implemented for PXELINUX and causes undefined symbol references for ISOLINUX, etc. Feel free to make the change again on top of the revert. The following changes since commit e7bd19def830e8341b1a100956345f1028740b9e:

Hi, well, I was finally able to build syslinux-5.11-pre8 from git, but the system doesn't boot with the self-compiled version. All I see is: http://666kb.com/i/cfplluqpcy6owptq3.jpg Build log can be found in http://www.syslinux.org/archives/2013-July/020452.html After I installed the self-compiled syslinux version, I run this commands: # cd /boot/extlinux # rm -rf *.c32 # extlinux

> On 2/6/19 11:44 AM, Joakim Tjernlund wrote: > > On Wed, 2019-02-06 at 11:34 -0800, H. Peter Anvin wrote: > > > > Great, that tree now against a somewhat old gnu-efi though. > > > > To build against >= 3.0.8 I need to do: > > #gnu-efi >= 3.0.8 has memset/memcpy defined causing multiple syms errors > > sed -i 's/LDFLAGS =/LDFLAGS =

Hello all, Does anyone have any inside why I can't get the below simple C API test to link? This is on a 32-bit Gentoo Linux system and LLVM TOT which was compiled with enable-optimized, gcc is 4.3.2. 15:26|melis at juggle2:~/c/llvmpy> cat t.c #include "llvm-c/Core.h" int main() { LLVMContextRef ctx; ctx = LLVMContextCreate(); return 0; } 15:29|melis at

Hi! I'm trying to learn LLVM and I want to compile the Kaleidoscope compiler. according to: http://llvm.org/docs/tutorial/LangImpl3.html I'm compiling it with: clang++ -g -O3 test.cpp `llvm-config --cppflags --ldflags --libs core` -o toy and it indeed works. The problem is that when using eclipse it forces me to divide the compilation into two steps: g++ -O0 -g3 -Wall -c

Eugene, how about below? $ clang clangtest.cpp `llvm-config --ldflags --libs core` (I guess linking order would be) 2012/7/18 Eugene <code_ep at yahoo.com>: > The output of `llvm-config --cppflags --ldflags --libs core support` and > `llvm-config --cppflags --ldflags --libs core` is the same. I've also tried specifying -lLLVMSupport manually. Same result. > > --Eugene >

Hi, This series targets automatic boot menu generation, but most of it is the Lua upgrade, because I got tired reading deprecated API docs. It's mostly a straightforward forward port of the earlier Syslinux specific changes to Lua 5.1, except that: * I chose the add a stub getenv() implementation to the COM32 API instead of #ifdefing out all the references in Lua, and * I kept oslib

Am 22.05.13 19:32, schrieb Kaylor, Andrew: > If you send me details about how you're building this I'll look into it. Thanks. I forgot to mention it's LLVM 3.2 on Ubuntu 12.10. The command line is: $ g++-4.7 ExecutionEngineTest.cpp $(llvm-config --cxxflags --ldflags --libs) -lpthread -ldl $ g++-4.7 -static ExecutionEngineTest.cpp $(llvm-config --cxxflags --ldflags --libs)

"Paul Melis" <llvm at assumetheposition.nl> writes: > 15:29|melis at juggle2:~/c/llvmpy> gcc -W -Wall -o blah `llvm-config --cflags > --ldflags --libs all` t.c > /tmp/ccs4MbKp.o: In function `main': > t.c:(.text+0x21): undefined reference to `LLVMContextCreate' > collect2: ld returned 1 exit status > > 15:29|melis at juggle2:~/c/llvmpy> nm

On Tue, Nov 6, 2012 at 6:38 AM, Wojciech Daniło <wojtek.danilo.ml at gmail.com> wrote: > Hi! > I'm trying to learn LLVM and I want to compile the Kaleidoscope compiler. > according to: > http://llvm.org/docs/tutorial/LangImpl3.html > > I'm compiling it with: > clang++ -g -O3 test.cpp `llvm-config --cppflags --ldflags --libs core` -o > toy > > and it