hppa vDSO and compiler (non-)support
Hi,
since the "parisc: Add vDSO support" commit, I can no longer cross-build a hppa kernel. I see two issues:
1) CROSS32_COMPILE detection doesn't work here, as openSUSE provides hppa-suse-linux-* binaries. It's easy to overcome by "CROSS32_COMPILE=hppa-suse-linux-"
2) openSUSE doesn't provide any libc for hppa. So gcc doesn't provide libgcc.a and the build of vDSO fails.
So could vDSO be optional on hppa via KConfig?
I used to use the cross compiler to at least compile-check the following
tty drivers:arch/parisc/kernel/pdc_cons.odrivers/tty/serial/mux.odrivers/tty/serial/8250/8250_gsc.o
thanks,
Signature · 2 lines
js suse labs
Helge Deller
maintainerHi Jiri,
Thanks for testing on parisc!
Quoted 3 lines · Jiri Slaby
since the "parisc: Add vDSO support" commit, I can no longer cross-build a hppa kernel. I see two issues:
1)
CROSS32_COMPILEdetection doesn't work here, as openSUSE provides hppa-suse-linux-* binaries. It's easy to overcome by "CROSS32_COMPILE=hppa-suse-linux-"
How is it handled for other platforms like s390x? Would it make sense to add the detection for SUSE too?
Quoted 1 line
2) openSUSE doesn't provide any libc for hppa. So gcc doesn't provide libgcc.a and the build of vDSO fails.
libgcc.a comes with the compiler, I don't think you need libc for that. I'm currently installing opensuse to try myself though...
Quoted 1 line
So could vDSO be optional on hppa via KConfig?
The vDSO is one of the first things which is built during kernel build process. This is why you fail.
Making it optional doesn't make sense, because then the kernel wouldn't be able to start the user space processes.
Quoted 4 lines
I used to use the cross compiler to at least compile-check the following tty drivers:
arch/parisc/kernel/pdc_cons.odrivers/tty/serial/mux.odrivers/tty/serial/8250/8250_gsc.o
I assume you never built a full kernel, but stopped when building those modules? Without libgcc.a the kernel itself wouldn't have linked before either.
Helge
Helge Deller
maintainer* Helge Deller <[email protected]>:
Quoted 23 lines
Hi Jiri,
Thanks for testing on parisc!
Quoted 3 lines · Jiri Slaby
since the "parisc: Add vDSO support" commit, I can no longer cross-build a hppa kernel. I see two issues:
1)
CROSS32_COMPILEdetection doesn't work here, as openSUSE provides hppa-suse-linux-* binaries. It's easy to overcome by "CROSS32_COMPILE=hppa-suse-linux-"How is it handled for other platforms like s390x? Would it make sense to add the detection for SUSE too?
Quoted 1 line
2) openSUSE doesn't provide any libc for hppa. So gcc doesn't provide libgcc.a and the build of vDSO fails.
libgcc.a comes with the compiler, I don't think you need libc for that. I'm currently installing opensuse to try myself though...
Quoted 1 line
So could vDSO be optional on hppa via KConfig?
The vDSO is one of the first things which is built during kernel build process. This is why you fail.
Making it optional doesn't make sense, because then the kernel wouldn't be able to start the user space processes.
Quoted 7 lines
Quoted 4 lines
I used to use the cross compiler to at least compile-check the following tty drivers:
arch/parisc/kernel/pdc_cons.odrivers/tty/serial/mux.odrivers/tty/serial/8250/8250_gsc.oI assume you never built a full kernel, but stopped when building those modules? Without libgcc.a the kernel itself wouldn't have linked before either.
Below is a hackish patch which should allow you to build at least until those modules. The make will still fail when linking the vmlinux file, because libgcc.a provides the necessary low level symbols.
I'm currently not planning to include this patch, because it simply doesn't make sense. Maybe you could nevertheless try/use it? I'm open to any other ideas you may have.
IMHO, the only solution is, that libgcc.a gets included into the suse cross compiler rpm package.
Helge
arch/parisc/Makefile +2 -0
@@ -165,6 +165,7 @@ vmlinuz: bzImage $(OBJCOPY) $(boot)/bzImage $@ ifeq ($(KBUILD_EXTMOD),) +ifdef CONFIG_VDSO # We need to generate vdso-offsets.h before compiling certain files in kernel/. # In order to do that, we should use the archprepare target, but we can't since # asm-offsets.h is included in some files used to generate vdso-offsets.h, and
@@ -177,6 +178,7 @@ vdso_prepare: prepare0 $(build)=arch/parisc/kernel/vdso64 include/generated/vdso64-offsets.h) $(Q)$(MAKE) $(build)=arch/parisc/kernel/vdso32 include/generated/vdso32-offsets.h endif +endif PHONY += vdso_install
arch/parisc/include/asm/vdso.h +7 -0
@@ -2,6 +2,7 @@#ifndef __PARISC_VDSO_H__#define __PARISC_VDSO_H__ +#ifdef CONFIG_VDSO #ifndef __ASSEMBLY__#ifdef CONFIG_64BIT
@@ -15,6 +16,12 @@extern struct vdso_data *vdso_data;#endif /* __ASSEMBLY __ */ +#else /* CONFIG_VDSO */ + +#define VDSO64_SYMBOL (tsk, name) (0) +#define VDSO32_SYMBOL (tsk, name) (0) + +#endif /* CONFIG_VDSO */ /* Default link addresses for the vDSOs */ #define VDSO_LBASE 0
arch/parisc/kernel/Makefile +2 -0
@@ -41,6 +41,8 @@ obj-$(CONFIG_KEXEC_CORE) += kexec.o relocate_kernel.o obj-$(CONFIG_KEXEC_FILE) += kexec_file.o # vdso +ifdef CONFIG_VDSO obj-y += vdso.o obj-$(CONFIG_64BIT) += vdso64/ obj-y += vdso32/ +endif
Hi,
Quoted 10 lines · Helge Deller
Hi Jiri,
Thanks for testing on parisc!
Quoted 3 lines · Jiri Slaby
since the "parisc: Add vDSO support" commit, I can no longer cross-build a hppa kernel. I see two issues:
1)
CROSS32_COMPILEdetection doesn't work here, as openSUSE provides hppa-suse-linux-* binaries. It's easy to overcome by "CROSS32_COMPILE=hppa-suse-linux-"How is it handled for other platforms like s390x?
s390 simply uses CC for vdso32:cmd_vdso32cc = $(CC) $(c_flags) -c -o $@ $<
Quoted 1 line
Would it make sense to add the detection for SUSE too?
Maybe.
Quoted 3 lines
Quoted 1 line
2) openSUSE doesn't provide any libc for hppa. So gcc doesn't provide libgcc.a and the build of vDSO fails.
libgcc.a comes with the compiler, I don't think you need libc for that.
I was told glibc is needed to build libgcc.a.
Quoted 8 lines
I'm currently installing opensuse to try myself though...
Quoted 1 line
So could vDSO be optional on hppa via KConfig?
The vDSO is one of the first things which is built during kernel build process. This is why you fail.
Making it optional doesn't make sense, because then the kernel wouldn't be able to start the user space processes.
Quoted 7 lines
Quoted 4 lines
I used to use the cross compiler to at least compile-check the following tty drivers:
arch/parisc/kernel/pdc_cons.odrivers/tty/serial/mux.odrivers/tty/serial/8250/8250_gsc.oI assume you never built a full kernel, but stopped when building those modules? Without libgcc.a the kernel itself wouldn't have linked before either.
Correct, I am only build-testing parisc-only drivers when doing global tty changes.
thanks,
Signature · 2 lines
js suse labs
Quoted 12 lines · Jiri Slaby
Hi,
Quoted 9 lines · Helge Deller
Hi Jiri,
Thanks for testing on parisc!
Quoted 3 lines · Jiri Slaby
since the "parisc: Add vDSO support" commit, I can no longer cross-build a hppa kernel. I see two issues:
1)
CROSS32_COMPILEdetection doesn't work here, as openSUSE provides hppa-suse-linux-* binaries. It's easy to overcome by "CROSS32_COMPILE=hppa-suse-linux-"
Quoted 8 lines
Quoted 1 line
How is it handled for other platforms like s390x?
s390 simply uses CC for vdso32:
cmd_vdso32cc= $(CC) $(c_flags) -c -o $@ $<Quoted 1 line
Would it make sense to add the detection for SUSE too?
Maybe.
So, could 1) be fixed on the Kconfig side? Or should I (people running SUSE) use "CROSS32_COMPILE=hppa-suse-linux-"?
Quoted 5 lines
Quoted 3 lines
Quoted 1 line
2) openSUSE doesn't provide any libc for hppa. So gcc doesn't provide libgcc.a and the build of vDSO fails.
libgcc.a comes with the compiler, I don't think you need libc for that.
I was told glibc is needed to build libgcc.a.
2) was fixed on the compiler (SUSE) side. cross-hppa-gcc12-bootstrap was introduced -- note it's known to be a misnomer -- it should have been like s/-bootstrap/-baremetal/.
thanks,
Signature · 2 lines
js suse labs
Helge Deller
maintainerHello Jiri,
* Jiri Slaby <[email protected]>:
Quoted 10 lines · Jiri Slaby
Quoted 9 lines · Helge Deller
Quoted 8 lines · Jiri Slaby
Quoted 6 lines
since the "parisc: Add vDSO support" commit, I can no longer cross-build a hppa kernel. I see two issues:
1)
CROSS32_COMPILEdetection doesn't work here, as openSUSE provides hppa-suse-linux-* binaries. It's easy to overcome by "CROSS32_COMPILE=hppa-suse-linux-"
Quoted 5 lines
Quoted 2 lines
...
Quoted 1 line
Would it make sense to add the detection for SUSE too?
So, could 1) be fixed on the
Kconfigside? Or should I (people running SUSE) use "CROSS32_COMPILE=hppa-suse-linux-"?
Could you please try if this patch fixes it for you?
arch/parisc/Makefile +2 -2
@@ -42,7 +42,7 @@ export LD_BFD # Set default 32 bits cross compilers for vdso CC_ARCHES_32 = hppa hppa2.0 hppa1.1 -CC_SUFFIXES = linux linux-gnu unknown-linux-gnu +CC_SUFFIXES = linux linux-gnu unknown-linux-gnu suse-linux CROSS32_COMPILE := $(call cc-cross-prefix, \ $(foreach a,$(CC_ARCHES_32), \ $(foreach s,$(CC_SUFFIXES),$(a)-$(s)-)))
@@ -52,7 +52,7 @@ export CROSS32CC # Set default cross compiler for kernel build ifdef cross_compiling ifeq ($(CROSS_COMPILE),) - CC_SUFFIXES = linux linux-gnu unknown-linux-gnu + CC_SUFFIXES = linux linux-gnu unknown-linux-gnu suse-linux CROSS_COMPILE := $(call cc-cross-prefix, \ $(foreach a,$(CC_ARCHES), \ $(foreach s,$(CC_SUFFIXES),$(a)-$(s)-)))
Quoted 11 lines
Quoted 7 lines
Quoted 5 lines
Quoted 3 lines
2) openSUSE doesn't provide any libc for hppa. So gcc doesn't provide libgcc.a and the build of vDSO fails.
libgcc.a comes with the compiler, I don't think you need libc for that.
I was told glibc is needed to build libgcc.a.
2) was fixed on the compiler (SUSE) side. cross-hppa-gcc12-bootstrap was introduced -- note it's known to be a misnomer -- it should have been like s/-bootstrap/-baremetal/.
Great!
Helge
Hello,
Quoted 11 lines · Helge Deller
* Jiri Slaby <[email protected]>:
Quoted 10 lines · Jiri Slaby
Quoted 9 lines · Helge Deller
Quoted 8 lines · Jiri Slaby
Quoted 6 lines
since the "parisc: Add vDSO support" commit, I can no longer cross-build a hppa kernel. I see two issues:
1)
CROSS32_COMPILEdetection doesn't work here, as openSUSE provides hppa-suse-linux-* binaries. It's easy to overcome by "CROSS32_COMPILE=hppa-suse-linux-"
Quoted 7 lines
Quoted 5 lines
Quoted 2 lines
...
Quoted 1 line
Would it make sense to add the detection for SUSE too?
So, could 1) be fixed on the
Kconfigside? Or should I (people running SUSE) use "CROSS32_COMPILE=hppa-suse-linux-"?Could you please try if this patch fixes it for you?
Works like a charm:
$ make V=1 O=../a/arch/parisc/ ARCH=parisc -j6 drivers/tty/serial/mux.o ...
Quoted 2 lines
hppa-suse-linux-gcc <flags deleted> -o
drivers/tty/serial/mux.o/home/latest/linux/drivers/tty/serial/mux.cif hppa-suse-linux-objdump -hdrivers/tty/serial/mux.o| ...; fi
Thanks.
Quoted 22 lines
arch/parisc/Makefile +2
-2@@ -42,7 +42,7 @@ export LD_BFD # Set default 32 bits cross compilers for vdso CC_ARCHES_32 = hppa hppa2.0 hppa1.1 -CC_SUFFIXES = linux linux-gnu unknown-linux-gnu +CC_SUFFIXES = linux linux-gnu unknown-linux-gnu suse-linux CROSS32_COMPILE := $(call cc-cross-prefix, \ $(foreach a,$(CC_ARCHES_32), \ $(foreach s,$(CC_SUFFIXES),$(a)-$(s)-)))@@ -52,7 +52,7 @@ export CROSS32CC # Set default cross compiler for kernel build ifdef cross_compiling ifeq ($(CROSS_COMPILE),) - CC_SUFFIXES = linux linux-gnu unknown-linux-gnu + CC_SUFFIXES = linux linux-gnu unknown-linux-gnu suse-linux CROSS_COMPILE := $(call cc-cross-prefix, \ $(foreach a,$(CC_ARCHES), \ $(foreach s,$(CC_SUFFIXES),$(a)-$(s)-)))
Signature · 3 lines
-- js suse labs
Helge Deller
maintainerQuoted 22 lines · Jiri Slaby
Hello,
Quoted 11 lines · Helge Deller
* Jiri Slaby <[email protected]>:
Quoted 10 lines · Jiri Slaby
Quoted 9 lines · Helge Deller
Quoted 8 lines · Jiri Slaby
Quoted 6 lines
since the "parisc: Add vDSO support" commit, I can no longer cross-build a hppa kernel. I see two issues:
1)
CROSS32_COMPILEdetection doesn't work here, as openSUSE provides hppa-suse-linux-* binaries. It's easy to overcome by "CROSS32_COMPILE=hppa-suse-linux-"Quoted 7 lines
Quoted 5 lines
Quoted 2 lines
...
Quoted 1 line
Would it make sense to add the detection for SUSE too?
So, could 1) be fixed on the
Kconfigside? Or should I (people running SUSE) use "CROSS32_COMPILE=hppa-suse-linux-"?Could you please try if this patch fixes it for you?
Quoted 7 lines
Works like a charm:
$ make V=1 O=../a/arch/parisc/ ARCH=parisc -j6 drivers/tty/serial/mux.o ...Quoted 2 lines
hppa-suse-linux-gcc <flags deleted> -o
drivers/tty/serial/mux.o/home/latest/linux/drivers/tty/serial/mux.cif hppa-suse-linux-objdump -hdrivers/tty/serial/mux.o| ...; fiThanks.
Great!
I've queued up a patch in for-next...
Helge
Quoted 24 lines
Quoted 23 lines
arch/parisc/Makefile +0
-0@@ -42,7 +42,7 @@ export LD_BFD # Set default 32 bits cross compilers for vdso
CC_ARCHES_32= hppa hppa2.0 hppa1.1arch/parisc/Makefile +1
-1-CC_SUFFIXES = linux linux-gnu unknown-linux-gnu +CC_SUFFIXES = linux linux-gnu unknown-linux-gnu suse-linux
CROSS32_COMPILE:= $(call cc-cross-prefix, \
$(foreach a,$(CC_ARCHES_32), \
$(foreach s,$(CC_SUFFIXES),$(a)-$(s)-)))arch/parisc/Makefile +0
-0@@ -52,7 +52,7 @@ export CROSS32CC # Set default cross compiler for kernel buildifdef
cross_compiling
ifeq ($(CROSS_COMPILE),)
-CC_SUFFIXES= linux linux-gnu unknown-linux-gnu +CC_SUFFIXES= linux linux-gnu unknown-linux-gnu suse-linuxCROSS_COMPILE:= $(call cc-cross-prefix, \
$(foreach a,$(CC_ARCHES), \
$(foreach s,$(CC_SUFFIXES),$(a)-$(s)-)))
Quoted 26 lines · Helge Deller
Quoted 25 lines · Jiri Slaby
Hello,
Quoted 11 lines · Helge Deller
* Jiri Slaby <[email protected]>:
Quoted 10 lines · Jiri Slaby
Quoted 9 lines · Helge Deller
Quoted 8 lines · Jiri Slaby
Quoted 6 lines
since the "parisc: Add vDSO support" commit, I can no longer cross-build a hppa kernel. I see two issues:
1)
CROSS32_COMPILEdetection doesn't work here, as openSUSE provides hppa-suse-linux-* binaries. It's easy to overcome by "CROSS32_COMPILE=hppa-suse-linux-"Quoted 7 lines
Quoted 5 lines
Quoted 2 lines
...
Quoted 1 line
Would it make sense to add the detection for SUSE too?
So, could 1) be fixed on the
Kconfigside? Or should I (people running SUSE) use "CROSS32_COMPILE=hppa-suse-linux-"?Could you please try if this patch fixes it for you?
Works like a charm:
$ make V=1 O=../a/arch/parisc/ ARCH=parisc -j6 drivers/tty/serial/mux.o ...
Quoted 8 lines
Quoted 4 lines
Quoted 2 lines
hppa-suse-linux-gcc <flags deleted> -o
drivers/tty/serial/mux.o/home/latest/linux/drivers/tty/serial/mux.cif hppa-suse-linux-objdump -hdrivers/tty/serial/mux.o| ...; fiThanks.
Great!
I've queued up a patch in for-next...
Does that also fix the build problems now seen in mainline ?
Building parisc64:generic-64bit_defconfig ... failed
--------------
Error log:arch/parisc/kernel/vdso64/Makefile:30: FORCE prerequisite is missing arch/parisc/kernel/vdso32/sigtramp.S: Assembler messages:arch/parisc/kernel/vdso32/sigtramp.S:39: Error: unknown pseudo-op: .proc' arch/parisc/kernel/vdso32/sigtramp.S:40: Error: unknown pseudo-op: .callinfo' arch/parisc/kernel/vdso32/sigtramp.S:41: Error: unknown pseudo-op: .entry' arch/parisc/kernel/vdso32/sigtramp.S:44: Error: no such instruction: ldi 0,%r25' arch/parisc/kernel/vdso32/sigtramp.S:45: Error: no such instruction: ldi 173,%r20' arch/parisc/kernel/vdso32/sigtramp.S:46: Error: no such instruction: ble 0x100(%sr2,%r0)' arch/parisc/kernel/vdso32/sigtramp.S:49: Error: no such instruction: ldi 1,%r25' arch/parisc/kernel/vdso32/sigtramp.S:50: Error: no such instruction: ldi 173,%r20' arch/parisc/kernel/vdso32/sigtramp.S:51: Error: no such instruction: ble 0x100(%sr2,%r0)' arch/parisc/kernel/vdso32/sigtramp.S:54: Error: unknown pseudo-op: .exit' arch/parisc/kernel/vdso32/sigtramp.S:55: Error: unknown pseudo-op: .procend' arch/parisc/kernel/vdso32/sigtramp.S:76: Error: unknown pseudo-op: .stringz' arch/parisc/kernel/vdso32/restart_syscall.S: Assembler messages:arch/parisc/kernel/vdso32/restart_syscall.S:16: Error: bad or irreducible absolute expression arch/parisc/kernel/vdso32/restart_syscall.S:16: Error: junk at end of line, first unrecognized character is :' arch/parisc/kernel/vdso32/restart_syscall.S:26: Error: no such instruction: ldw 0(%sp),%r31' arch/parisc/kernel/vdso32/restart_syscall.S:29: Error: no such instruction: be 0x100(%sr2,%r0)' arch/parisc/kernel/vdso32/restart_syscall.S:30: Error: no such instruction: ldi 0,%r20' arch/parisc/kernel/vdso32/restart_syscall.S:32: Error: .cfi_endproc without corresponding .cfi_startproc make[2]: *** [arch/parisc/kernel/vdso32/Makefile:34: arch/parisc/kernel/vdso32/restart_syscall.o] Error 1 make[2]: *** Waiting for unfinished jobs....
make[2]: *** [arch/parisc/kernel/vdso32/Makefile:34: arch/parisc/kernel/vdso32/sigtramp.o] Error 1 make[1]: *** [arch/parisc/Makefile:177: vdso_prepare] Error 2
make: *** [Makefile:219: __sub-make] Error 2
This is with hppa64-linux-gcc (GCC) 11.2.0.
Thanks,
Guenter
Helge Deller
maintainerQuoted 1 line · Guenter Roeck
Does that also fix the build problems now seen in mainline ?
No.
Quoted 14 lines
Building parisc64:generic-64bit_defconfig ... failed
--------------
Error log:arch/parisc/kernel/vdso64/Makefile:30: FORCE prerequisite is missingarch/parisc/kernel/vdso32/sigtramp.S: Assembler messages:arch/parisc/kernel/vdso32/sigtramp.S:39: Error: unknown pseudo-op: `.proc'
...arch/parisc/kernel/vdso32/restart_syscall.S:32: Error: .cfi_endproc without corresponding .cfi_startproc make[2]: *** [arch/parisc/kernel/vdso32/Makefile:34:arch/parisc/kernel/vdso32/restart_syscall.o] Error 1 make[2]: *** Waiting for unfinished jobs....
make[2]: *** [arch/parisc/kernel/vdso32/Makefile:34:arch/parisc/kernel/vdso32/sigtramp.o] Error 1 make[1]: *** [arch/parisc/Makefile:177:vdso_prepare] Error 2
make: *** [Makefile:219: __sub-make] Error 2
Quoted 1 line
This is with hppa64-linux-gcc (GCC) 11.2.0.
Can you check if you have the 32-bit compiler (hppa-linux-gcc) installed too? The errors above happen when building the 32-bit vDSO, for which you need the 32-bit compiler.
Helge
Quoted 19 lines · Helge Deller
Quoted 1 line · Guenter Roeck
Does that also fix the build problems now seen in mainline ?
No.
Quoted 14 lines
Building parisc64:generic-64bit_defconfig ... failed
--------------
Error log:arch/parisc/kernel/vdso64/Makefile:30: FORCE prerequisite is missingarch/parisc/kernel/vdso32/sigtramp.S: Assembler messages:arch/parisc/kernel/vdso32/sigtramp.S:39: Error: unknown pseudo-op: `.proc'
...arch/parisc/kernel/vdso32/restart_syscall.S:32: Error: .cfi_endproc without corresponding .cfi_startproc make[2]: *** [arch/parisc/kernel/vdso32/Makefile:34:arch/parisc/kernel/vdso32/restart_syscall.o] Error 1 make[2]: *** Waiting for unfinished jobs....
make[2]: *** [arch/parisc/kernel/vdso32/Makefile:34:arch/parisc/kernel/vdso32/sigtramp.o] Error 1 make[1]: *** [arch/parisc/Makefile:177:vdso_prepare] Error 2
make: *** [Makefile:219: __sub-make] Error 2
Quoted 5 lines
Quoted 1 line
This is with hppa64-linux-gcc (GCC) 11.2.0.
Can you check if you have the 32-bit compiler (hppa-linux-gcc) installed too? The errors above happen when building the 32-bit vDSO, for which you need the 32-bit compiler.
Yes, I do, but that doesn't help much if I want to build a 64-bit target such as generic-64bit_defconfig. Am I missing something ?
Guenter
Helge Deller
maintainerQuoted 20 lines · Guenter Roeck
Quoted 19 lines · Helge Deller
Quoted 1 line · Guenter Roeck
Does that also fix the build problems now seen in mainline ?
No.
Quoted 14 lines
Building parisc64:generic-64bit_defconfig ... failed
--------------
Error log:arch/parisc/kernel/vdso64/Makefile:30: FORCE prerequisite is missingarch/parisc/kernel/vdso32/sigtramp.S: Assembler messages:arch/parisc/kernel/vdso32/sigtramp.S:39: Error: unknown pseudo-op: `.proc'
...arch/parisc/kernel/vdso32/restart_syscall.S:32: Error: .cfi_endproc without corresponding .cfi_startproc make[2]: *** [arch/parisc/kernel/vdso32/Makefile:34:arch/parisc/kernel/vdso32/restart_syscall.o] Error 1 make[2]: *** Waiting for unfinished jobs....
make[2]: *** [arch/parisc/kernel/vdso32/Makefile:34:arch/parisc/kernel/vdso32/sigtramp.o] Error 1 make[1]: *** [arch/parisc/Makefile:177:vdso_prepare] Error 2
make: *** [Makefile:219: __sub-make] Error 2
Quoted 8 lines
Quoted 5 lines
Quoted 1 line
This is with hppa64-linux-gcc (GCC) 11.2.0.
Can you check if you have the 32-bit compiler (hppa-linux-gcc) installed too? The errors above happen when building the 32-bit vDSO, for which you need the 32-bit compiler.
Yes, I do, but that doesn't help much if I want to build a 64-bit target such as generic-64bit_defconfig. Am I missing something ?
The 64-bit PA-RISC kernel now includes a built-in a 32-bit and a 64-bit vDSO for userspace. To build the 32-bit vDSO (vdso32) you need the 32-bit hppa compiler installed. That's what's being done above - see the path: arch/parisc/kernel/vdso32/ Can you try "make V=1" to see the command line?
Helge
Quoted 27 lines · Helge Deller
Quoted 26 lines · Guenter Roeck
Quoted 24 lines · Helge Deller
Quoted 1 line · Guenter Roeck
Does that also fix the build problems now seen in mainline ?
No.
Quoted 14 lines
Building parisc64:generic-64bit_defconfig ... failed
--------------
Error log:arch/parisc/kernel/vdso64/Makefile:30: FORCE prerequisite is missingarch/parisc/kernel/vdso32/sigtramp.S: Assembler messages:arch/parisc/kernel/vdso32/sigtramp.S:39: Error: unknown pseudo-op: `.proc'
...arch/parisc/kernel/vdso32/restart_syscall.S:32: Error: .cfi_endproc without corresponding .cfi_startproc make[2]: *** [arch/parisc/kernel/vdso32/Makefile:34:arch/parisc/kernel/vdso32/restart_syscall.o] Error 1 make[2]: *** Waiting for unfinished jobs....
make[2]: *** [arch/parisc/kernel/vdso32/Makefile:34:arch/parisc/kernel/vdso32/sigtramp.o] Error 1 make[1]: *** [arch/parisc/Makefile:177:vdso_prepare] Error 2
make: *** [Makefile:219: __sub-make] Error 2Quoted 1 line
This is with hppa64-linux-gcc (GCC) 11.2.0.
Can you check if you have the 32-bit compiler (hppa-linux-gcc) installed too? The errors above happen when building the 32-bit vDSO, for which you need the 32-bit compiler.
Quoted 8 lines
Quoted 2 lines
Yes, I do, but that doesn't help much if I want to build a 64-bit target such as generic-64bit_defconfig. Am I missing something ?
The 64-bit PA-RISC kernel now includes a built-in a 32-bit and a 64-bit vDSO for userspace. To build the 32-bit vDSO (vdso32) you need the 32-bit hppa compiler installed. That's what's being done above - see the path:
arch/parisc/kernel/vdso32/Can you try "make V=1" to see the command line?
I am currently bisecting another problem. I'll try that afterwards. Either case, how does one specify two cross compilers with two different prefixes on the command line ?
Guenter
Helge Deller
maintainerQuoted 5 lines · Guenter Roeck
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Building parisc64:generic-64bit_defconfig ... failed
--------------
Error log:arch/parisc/kernel/vdso64/Makefile:30: FORCE prerequisite is missingarch/parisc/kernel/vdso32/sigtramp.S: Assembler messages:
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
arch/parisc/kernel/vdso32/sigtramp.S:39: Error: unknown pseudo-op: `.proc'
...arch/parisc/kernel/vdso32/restart_syscall.S:32: Error: .cfi_endproc without corresponding .cfi_startproc make[2]: *** [arch/parisc/kernel/vdso32/Makefile:34:arch/parisc/kernel/vdso32/restart_syscall.o] Error 1 make[2]: *** Waiting for unfinished jobs....
make[2]: *** [arch/parisc/kernel/vdso32/Makefile:34:arch/parisc/kernel/vdso32/sigtramp.o] Error 1 make[1]: *** [arch/parisc/Makefile:177:vdso_prepare] Error 2
make: *** [Makefile:219: __sub-make] Error 2
To recap - the solution was to add CROSS32_COMPILE=hppa-linux- , e.g.:
make ARCH=parisc CROSS_COMPILE=hppa64-linux- CROSS32_COMPILE=hppa-linux-
The better solution (for kernel >= v5.17) is to simply leave out the CROSS_COMPILE/CROSS32_COMPILE parameters and let the Makefile autodetect everything:
make ARCH=parisc -> 32bit kernel
make ARCH=parisc64 -> 64bit kernel
It's now documented in the Wiki:
https://parisc.wiki.kernel.org/index.php/Cross_compiler_toolchain#How_to_build_the_kernel
Helge