similar to: [PATCH] do not use -R on ppc to link shared objects

Displaying 20 results from an estimated 2000 matches similar to: "[PATCH] do not use -R on ppc to link shared objects"

2004 Sep 14
1
Re: got pointer wrong in shared klibc binary
On Wed, Sep 15, 2004 at 10:48:02AM +0930, Alan Modra wrote: > After using SHAREDFLAGS = -Ttext 0x0f000200 on ppc64 (which I see you > suggested in another email), I see the problem you're talking about. > > klibc is fundamentally broken on ppc64. You just can't call into > another chunk of code (klibc.so in this case) which has a separate toc > and expect things to
2003 Mar 03
0
Re: [BK PATCH] klibc for 2.5.63
On Mon, Feb 24, 2003 at 05:26:32PM -0800, H. Peter Anvin wrote: > Greg has taken on the job of integrating klibc with the kernel, but > please post klibc bug reports to the klibc mailing list at > <klibc@zytor.com>. To avoid annoying warning from gcc I had to check for compatibility with -falign-* like we do in arch/i386/Makefile. check_usergcc located in top-level makefile to
2019 Jan 20
0
[klibc:master] Use -Ttext-segment to link shared library on all arches
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
2005 Jul 26
2
[PATCH] better kbuild integration
Following patch improves integration with kbuild. With a future kernel (2.6.14-rc) it now has working support for 'make clean'. Included is an example of how to compile an early userspace program. I selected gzip as the most simple one for this - and left out all the links to different names (gunzip etc.) Before proceeding with this I need some inputs on what functionality is required by
2005 Jul 29
1
move kbuild files to reflect dir structure in kernel
To make it more obvious where the files are supposed to end up move files so they reflect the directory structure in the kernel: mkdir scripts mv kernel/Kbuild.* scripts/ mkdir usr mv kernel/Kbuild usr rmdir kernel Furthermore: - updated cp-to-kernel to refelct new directory layout - teach cp-to-kernel to place gzip right under usr/ - Add '#' in front of comment in usr/Kbuild --- I
2020 Jan 27
4
[PATCH] support llvm's lld
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
2005 Feb 10
1
[PATCH] make DEBUG=true
udev knows about DEBUG=true and builds a debug binary. Maybe klibc should do the same? Was there a reason for -g in the i386 MCONFIG? Index: MCONFIG =================================================================== --- MCONFIG (revision 1003) +++ MCONFIG (working copy) @@ -62,5 +62,11 @@ # include $(KLIBSRC)/arch/$(ARCH)/MCONFIG +ifeq ($(DEBUG),true) +STRIP = /bin/true
2006 May 11
0
[patch] klibc: merge s390 and s390x
Merge s390 and s390x into s390. Compiled and tested on s390/s390x and i386. Also cross compilation for s390/s390x tested. This patch shouldn't break the build of any architecture. Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com> --- Makefile | 1 scripts/Kbuild.install | 4 +- scripts/Kbuild.klibc
2006 May 24
1
[patch] klibc: merge s390/s390x 2nd try
From: Heiko Carstens <heiko.carstens@de.ibm.com> Merge s390 and s390x into s390. Patch is against current linux-2.6-klibc tree and seems to work. Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com> --- As a side note: a bitops patch is missing to make this working. Martin will send it soon. If it's needed earlier I can send it as well. Makefile
2005 Jul 28
0
[PATCH] Use KLIBSRC + KLIBINC consistent in kbuild files
Factor out all kernel specific path's (those containing usr/) into two variables: KLIBSRC + KLIBINC. Set the variables in a kernel spcific Kbuild file. Sam commit e6f989c1597a837f4aecbd11083697184c089611 tree 93f88d7564bb9e4d4bc95fd455b842d0bd0fdc54 parent 8151f4a98f82fba4fe3b949f49da4ab8bba71501 author Sam Ravnborg <sam@mars.(none)> Thu, 28 Jul 2005 23:36:07 +0200 committer Sam
2019 Jan 18
0
[klibc:master] Kbuild: Remove KLIBCKERNELOBJ variable
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
2019 Jan 18
0
[klibc:master] x86_64: 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
2013 Dec 26
2
[PATCH] Update header locations for uapi & generated
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> ---
2020 Jul 25
0
[klibc:master] arch: Explicitly disable or enable executable stacks
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
2020 Jul 25
0
[klibc:master] Kbuild: support clang's lld
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
2020 Mar 27
1
[PATCH v2 2/5] Kbuild: support clang's lld
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 +-
2005 Jul 30
3
kbuild updates to klibc
Hi Peter & others. Here are three patches that does the following: #1 - Update kbuild part of klibc so make clean works Adds gzip including a sample kbuild file #2 - Factor out definition of usr/ to two variables #3 - Move kbuild files to reflect location in the kernel As requested in earlier mail I need a bit of guidiance of what you expect from the kernel integrated parts of klibc.
2020 Jul 26
0
[kvm-unit-tests PATCH v3 0/4] Update patch set
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
2019 Jan 18
0
[klibc:master] x86_64: Reduce ld max-page-size option again
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
2019 Jan 05
0
x86_64: Use -Ttext-segment to avoid address collision
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