diff options
| author | Raptor Engineering Development Team <support@raptorengineering.com> | 2019-09-16 16:06:08 -0500 |
|---|---|---|
| committer | Raptor Engineering Development Team <support@raptorengineering.com> | 2019-09-27 15:57:23 -0500 |
| commit | 398a4b85d4374a35f580db998b854261a5a7db74 (patch) | |
| tree | 9464d1f07b64b6357c08b923e7fb4ba1ff4bf7cd /package/nvidia-driver/0001-use-LDFLAGS.patch | |
| parent | ef2bf42027bd0bce7691bbdf9d2e7e67ef68fa79 (diff) | |
| download | buildroot-2019.02-op-build.tar.gz buildroot-2019.02-op-build.zip | |
Initial pass at removing binary-only, unlicensed, and proprietary packages from buildroot tree2019.02-op-build
Note that DAHDI is only being removed due to poor packaging -- it does not require binary
firmware on some cards, but the buildroot packaging for it unconditionally pulls in binary-only
firmware regardless.
Diffstat (limited to 'package/nvidia-driver/0001-use-LDFLAGS.patch')
| -rw-r--r-- | package/nvidia-driver/0001-use-LDFLAGS.patch | 48 |
1 files changed, 0 insertions, 48 deletions
diff --git a/package/nvidia-driver/0001-use-LDFLAGS.patch b/package/nvidia-driver/0001-use-LDFLAGS.patch deleted file mode 100644 index 7b7df80988..0000000000 --- a/package/nvidia-driver/0001-use-LDFLAGS.patch +++ /dev/null @@ -1,48 +0,0 @@ -kernel: use LDFLAGS when linking modules - -Currently, linking module objects is simply using $(LD), assuming that -the default emulation is correct for the current architecture. - -However, that might not be the case when the toolchain default is not -the same as the current arch. For example, if the toolchain defaults to -i386 and is capable of x86_64, and we're targetting x86_64 (or the -opposite), the link would fail because the ld emulation is incorrect: - - .../i686-pc-linux-gnu-ld: Relocatable linking with relocations from - format elf64-x86-64 (.../nvidia-driver-370.23/kernel/nvidia/nv-frontend.o) - to format elf32-i386 (.../nvidia-driver-370.23/kernel/nvidia/nv-interface.o) - is not supported - -Add use of $(LDFLAGS) when doing the link, as the kernel provides the -proper emulation in those. - -Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> - ---- -Issue reported upstream: - https://devtalk.nvidia.com/default/topic/958653/ - -diff -durN nvidia-driver-370.23.orig/kernel/nvidia/nvidia.Kbuild nvidia-driver-370.23/kernel/nvidia/nvidia.Kbuild ---- nvidia-driver-370.23.orig/kernel/nvidia/nvidia.Kbuild 2016-08-09 01:57:50.000000000 +0200 -+++ nvidia-driver-370.23/kernel/nvidia/nvidia.Kbuild 2016-08-20 12:25:02.780233423 +0200 -@@ -87,7 +87,7 @@ - always += $(NVIDIA_INTERFACE) - - $(obj)/$(NVIDIA_INTERFACE): $(addprefix $(obj)/,$(NVIDIA_OBJECTS)) -- $(LD) -r -o $@ $^ -+ $(LD) $(LDFLAGS) -r -o $@ $^ - - - # -diff -durN nvidia-driver-370.23.orig/kernel/nvidia-modeset/nvidia-modeset.Kbuild nvidia-driver-370.23/kernel/nvidia-modeset/nvidia-modeset.Kbuild ---- nvidia-driver-370.23.orig/kernel/nvidia-modeset/nvidia-modeset.Kbuild 2016-08-09 01:43:19.000000000 +0200 -+++ nvidia-driver-370.23/kernel/nvidia-modeset/nvidia-modeset.Kbuild 2016-08-20 12:25:39.596772662 +0200 -@@ -70,7 +70,7 @@ - always += $(NVIDIA_MODESET_INTERFACE) - - $(obj)/$(NVIDIA_MODESET_INTERFACE): $(addprefix $(obj)/,$(NVIDIA_MODESET_OBJECTS)) -- $(LD) -r -o $@ $^ -+ $(LD) $(LDFLAGS) -r -o $@ $^ - - # - # Register the conftests needed by nvidia-modeset.ko |
