similar to: [klibc:master] i386: Use -Ttext-segment to avoid address collision

Commit-ID: 2a705525e0816f9d708d7c41688f6bcb127374fe Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=2a705525e0816f9d708d7c41688f6bcb127374fe Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Sat, 5 Jan 2019 20:59:33 +0000 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Fri, 18 Jan 2019 03:10:14 +0000 [klibc] x86_64: Use -Ttext-segment

Building klibc for x86_64 with binutils 2.31 adds an extra .note.gnu.property section to klibc.so, the address of which is not affected by the -Ttext option. Loading a klibc executable then fails with the following kernel log message: 9409 (sh.shared): Uhuuh, elf segment at 0000000000200000 requested but the memory is mapped already I don't exactly see why this is happening, but it is

Commit-ID: 72d6d78a8f0d24a64911c246487402c81b4beb9d Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=72d6d78a8f0d24a64911c246487402c81b4beb9d Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Sun, 20 Jan 2019 19:41:47 +0000 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sun, 20 Jan 2019 21:15:17 +0000 [klibc] Use -Ttext-segment to link

Commit-ID: ad72c27485b86171153ab26a1c1035f8e9bbd5e3 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=ad72c27485b86171153ab26a1c1035f8e9bbd5e3 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Sun, 6 Jan 2019 20:50:56 +0000 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Fri, 18 Jan 2019 03:10:14 +0000 [klibc] Kbuild: Remove

In the v3.6 kernel, many of the headers were split out into a uapi variant. klibc should be using those variants to compile. There is also a generated subdir, to seperate out generated headers. The old kernel header location needs to be included as well, because linux/compiler.h is available only in the base include directory. Signed-off-by: Robin H. Johnson <robbat2 at gentoo.org> ---

When using clang+llvm and lld, I get the following error: ld.lld: error: -Ttext-segment is not supported. Use --image-base if you intend to set the base address Let's test whether linker is lld and use --image-base instead of -Ttext-segment. See llvm's rationale for not supporting -Ttext-segment: https://github.com/llvm/llvm-project/commit/4dc2fb123dcfe9a97ad6f3a1135053b74efd0bc9 Note

Commit-ID: eaca2447991709cddfd8c42f3fa4a2e890d2cce8 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=eaca2447991709cddfd8c42f3fa4a2e890d2cce8 Author: Bill Wendling <morbo at google.com> AuthorDate: Sun, 29 Mar 2020 04:38:31 -0700 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 25 Jul 2020 20:45:34 +0100 [klibc] Kbuild: support clang's

From: Stanislav Fomichev <sdf at google.com> Clang's lld prefers the use of "-image-base" instead of "-Ttext-segment". Signed-off-by: Stanislav Fomichev <sdf at google.com> Signed-off-by: Bill Wendling <morbo at google.com> --- Makefile | 3 +++ usr/klibc/arch/i386/MCONFIG | 2 +- usr/klibc/arch/mips64/MCONFIG | 2 +-

Commit-ID: 048bfb0df170d4a43142adcee8a2dffdfc2c1e9f Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=048bfb0df170d4a43142adcee8a2dffdfc2c1e9f Author: James Cowgill <james.cowgill at mips.com> AuthorDate: Fri, 2 Mar 2018 08:33:01 -0800 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Wed, 2 Jan 2019 03:08:04 +0000 [klibc] mips: use -Ttext-segment

On Sat, Jul 25, 2020 at 4:10 PM Ben Hutchings <ben at decadent.org.uk> wrote: > On Sat, 2020-07-25 at 15:16 -0700, Bill Wendling wrote: > > On Sat, Jul 25, 2020 at 2:56 PM Ben Hutchings <ben at decadent.org.uk> wrote: > > > On Sat, 2020-07-25 at 14:36 -0700, Bill Wendling wrote: > > > [...] > > > > I upstreamed a few patches to klibc to fix a few

Commit-ID: 27ad55131385821dfe85b0320f4d6ba8861ab7e5 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=27ad55131385821dfe85b0320f4d6ba8861ab7e5 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Wed, 29 Apr 2020 22:56:59 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 25 Jul 2020 17:33:29 +0100 [klibc] arch: Explicitly disable

This series fixes link/load issues I found on i386 with Debian's toolchain (gcc 8 with PIE as default, binutils 2.31). Ben. Ben Hutchings (2): [klibc] i386: Use -Ttext-segment to avoid address collision [klibc] Disable PIE scripts/Kbuild.klibc | 3 ++- usr/klibc/arch/i386/MCONFIG | 2 +- 2 files changed, 3 insertions(+), 2 deletions(-) -------------- next part -------------- A

Commit-ID: 0a14ced5d7d0c23ece5d2828cbdff6cb1c589b8d Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=0a14ced5d7d0c23ece5d2828cbdff6cb1c589b8d Author: James Cowgill <james.cowgill at mips.com> AuthorDate: Fri, 2 Mar 2018 14:48:21 +0000 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Wed, 2 Jan 2019 03:08:04 +0000 [klibc] mips64: compile with

Use $(LD_IMAGE_BASE_OPT) instead of hardcoding --Ttext-segment, which lld does not support. This allows either --Ttext-segment or -image-base to be emitted based on the linker. Signed-off-by: Andrew Delgadillo <adelg at google.com> --- usr/klibc/arch/arm64/MCONFIG | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/usr/klibc/arch/arm64/MCONFIG b/usr/klibc/arch/arm64/MCONFIG

Hello ppc32 users, I think I finally got the "official" answer on the ppc32 problem. Apparently some distributions build binutils so that it defaults to elf32ppc emulation rather than elf32ppclinux. This doesn't matter when using gcc, since gcc overrides the emulation explicitly, but it does matter when invoking ld directly like klibc does. This patch should hopefully take

Commit-ID: 13b9b8c904408fdf4a72b9ab991a5a52749b4bcf Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=13b9b8c904408fdf4a72b9ab991a5a52749b4bcf Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Sun, 15 Jul 2018 21:27:09 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Fri, 18 Jan 2019 03:10:14 +0000 [klibc] x86_64: Reduce ld

while this doesn't fix the problem that shared doesn't work there, it at least ensures that klibc.so and (e.g.) sh.shared do not try to occupy the same virtual addresses mips64 is also missing KLIBCSHAREDFLAGS and needs treatment Signed-off-by: Thorsten Glaser <tg at mirbsd.org> --- usr/klibc/arch/ia64/MCONFIG | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git

Building klibc with binutils 2.30 results in the following layout for klibc.so: Idx Name Size VMA LMA File off Algn 0 .text 0000d1ff 0000000000200200 0000000000200200 00000200 2**2 CONTENTS, ALLOC, LOAD, READONLY, CODE 1 .rodata 000031af 0000000000300000 0000000000300000 00100000 2**5

The *.shared targets require -shared on powerpc, and -R leads to linker errors. This patch makes the -R an arch define. ia64 at least requires -R. --- ash/Makefile +++ ash/Makefile 2003/11/27 15:04:02 @@ -36,7 +36,7 @@ $(STRIP) $(PROG) $(PROG).shared: $(OBJS) $(LIBS) - $(LD) $(LDFLAGS) -o $(PROG).shared -e main $(KLIBSRC)/interp.o $(OBJS) -R $(KLIBSRC)/libc.so $(LIBGCC) + $(LD) $(LDFLAGS)

hello hpa, here my birthday submission :) please pull: git pull git://git.debian.org/users/maks/klibc.git maks Sam fixed a longstanding x86_32 build bug, thus it seems a good time to flush the queue of the piled up patches, the shortlog tells it: Aurelien Jarno (1): [klibc] sh4: syscalls fixes Benjamin Cama (1): [klibc] fstype: btrfs size endianness fix Mike Waychison (2):