search for: search_dir

...for normal executables */ /* Copyright (C) 2014-2017 Free Software Foundation, Inc. Copying and distribution of this script, with or without modification, are permitted in any medium without royalty provided the copyright notice and this notice are preserved. */ OUTPUT_FORMAT(pei-x86-64) SEARCH_DIR("/usr/x86_64-pc-cygwin/lib"); SEARCH_DIR("/usr/lib"); SEARCH_DIR("/usr/lib/w32api"); SECTIONS { /* Make the virtual address and file offset synced if the alignment is lower than the target page size. */ . = SIZEOF_HEADERS; . = ALIGN(__section_alignment__);...

...; /* Copyright (C) 2014-2017 Free Software Foundation, Inc. > Copying and distribution of this script, with or without modification, > are permitted in any medium without royalty provided the copyright > notice and this notice are preserved. */ > OUTPUT_FORMAT(pei-x86-64) > SEARCH_DIR("/usr/x86_64-pc-cygwin/lib"); SEARCH_DIR("/usr/lib"); > SEARCH_DIR("/usr/lib/w32api"); > SECTIONS > { > /* Make the virtual address and file offset synced if the alignment is > lower than the target page size. */ > . = SIZEOF_HEADERS; >...

...There are many other directives that have command line option equivalents that are used to setup linking. You can pull symbols with EXTERN, add other files to link with INPUT, add groups of archives to be searched with GROUP, name the output file with OUTPUT, add new library path directories with SEARCH_DIR, etc… Also keep in mind that that linker scripts are usually "inlined" with other command line options. For example: ld foo.o --defsym=x=12 -Lbar -T beagle-ram.ld -lbaz bar.o As you said, it makes sense to parse it during command line argument parsing. -- Meador Inge CodeSourcery...

COFF lld doesn't support the linker script at the moment, and I'm sad to say that it is very unlikely to support that in the future. Linker script support is so huge that I can't imagine we really want it for COFF. GNU BFD linker supports it because the linker is built as an interpreter for the built-in linker script (and that's one of the reasons why GNU linker is by far more

Hello, I have a user who is trying to get LLD to link for the cygwin target: https://github.com/zig-lang/zig/issues/751 Currently the issue they are running into is needing to define a linker script, but the COFF driver (or MinGW driver) does not have support for that. Is there documentation or advice for how to use LLD to link for cygwin? As a starting point, which driver to use? Regards,

Hi all, Which are the command-line options available to pass linker script, library path etc.. to lld? I see minimal options listed, when i say, lld -flavor gnu -help Thanks in advance, -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150209/e7a6f7b8/attachment.html>

On Wed, Jan 2, 2013 at 12:04 PM, Shankar Easwaran <shankare at codeaurora.org> wrote: > You might want to look at the ELFLayout changes to see what functionality is > missing from that. > > The ELFLayoutOptions has a hook into reading the Linker script which needs > to be implemented. So, looking into it a bit, I think that ELFLayoutOptions is not the right place to parse the

Hello, I''m using kernel 3.1.0 and I have both / and /home as btrfs. I used suspend to ram quite often and never had a problem, but yesterday I''ve suspended to get into a plane and when I resumed my /home was all about input/output errors. Reboot did not help either. My root (/) did not suffer any problems. Today I''ve upgraded btrfs-progs to latest GIT and tried scrub

I was thinking specifically of the subset of the commands for dealing with files, for example INPUT, GROUP and SEARCH_DIR. I agree that it would not be wise to allow the full generality of linker scripts. Thinking about this a bit more I think my main concern is that we should try hard to make sure that any commands that are embedded in an object file are compatible with any equivalent linker script commands. On 8 Ja...

...r directives that > have command line option equivalents that are used to setup linking. You can pull symbols > with EXTERN, add other files to link with INPUT, add groups of archives to be searched > with GROUP, name the output file with OUTPUT, add new library path directories > with SEARCH_DIR, etc… > > Also keep in mind that that linker scripts are usually "inlined" with other command line > options. For example: > > ld foo.o --defsym=x=12 -Lbar -T beagle-ram.ld -lbaz bar.o This is different. There are things in the command line which would a) add symbols...

On Jan 9, 2013, at 12:29 PM, Sean Silva wrote: >> Maybe the first version could be just ELF centric. > > The consensus in this thread seems to be that it should be in the > frontend. Nick pointed out that since linker scripts can define > symbols, they need to be handled before the writer; I don't see any > way to avoid that. Could you elaborate on the concrete reasons

On Mon, Jan 8, 2018 at 3:22 AM, Peter Smith <peter.smith at linaro.org> wrote: > On 8 January 2018 at 09:32, James Henderson via llvm-dev > <llvm-dev at lists.llvm.org> wrote: > > On 8 January 2018 at 08:14, Rui Ueyama <ruiu at google.com> wrote: > >> > >> On Mon, Jan 8, 2018 at 3:55 AM, Sean Silva via llvm-dev > >> <llvm-dev at

On Wed, Jan 9, 2013 at 9:13 AM, <shankare at codeaurora.org> wrote: > I dont think any other format has the functionality of sections and > segments with segment and section permissions etc. > > Are you planning to mimic 1-1 lld to ld linker script functionality ? No, there's lots of arcane things that GNU ld has (like compatibility with a completely different linker script

...alised data memory corruption ldlinux: Make the default execute type KT_KERNEL ldlinux: Disable VGA graphics when loading a kernel ldlinux: Don't alloc initramfs unless initrd= is specified mk: Don't link against compiler's version of libgcc core: Abstract search_config() into search_dirs() com32/Makefile | 4 +- com32/elflink/ldlinux/Makefile | 5 +- com32/elflink/ldlinux/cli.c | 36 ++------------ com32/elflink/ldlinux/execute.c | 43 ++++++++-------- com32/elflink/ldlinux/ipappend.c | 58 --------------------- com32/elflink/ldlin...

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

Hello, I am having some issues with the installation of the Icecast2 software on my CentOS 5.3 x64 machine. I am attempting to install from a source RPM provided by the developer. Upon executing: # rpmbuild --rebuild icecast-2.3.2-0.src.rpm Normal compilation takes place until the following error is thrown out: /usr/lib64/libxslt.so: undefined reference to `xmlXPathContextSetCache'

Hi gang, I was a little surprised to see that patch go by recently which fixed an endian bug. I went to see how sparse checking looked and it was.. broken. I got it going again in my Fedora environment. Most of the patches are just cleanups, but there *were* three real bugs lurking in all that sparse warning spam. So I maintain that it''s worth our time to keep it going and fix