Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Build failing after recent vadvise changes

On 26.12.2017 15:13, Tom Ivar Helbekkmo wrote:
> I just updated from CVS again today, and, following the advice in
> UPDATING, started a build without -u.  That didn't do the trick:
> /usr/tools/bin/x86_64--netbsd-gcc -nodefaultlibs -shared -Wl,-soname, -Wl,--warn-shared-textrel -Wl, -Wl,-z,initfirst   --sysroot=/usr/arena/amd64 -Wl,-z,relro -Wl,--warn-shared-textrel  -o  -Wl,-rpath,/lib  -L=/lib -Wl,-x  -Wl,--whole-archive libc_pic.a  -Wl,--no-whole-archive -lgcc 
> /usr/tools/lib/gcc/x86_64--netbsd/5.5.0/../../../../x86_64--netbsd/bin/ld: libc_pic.a(vadvise.pico): relocation R_X86_64_32 against undefined symbol `SYS_vadvise' can not be used when making a shared object; recompile with -fPIC
> /usr/tools/lib/gcc/x86_64--netbsd/5.5.0/../../../../x86_64--netbsd/bin/ld: final link failed: Nonrepresentable section on output
> collect2: error: ld returned 1 exit status
> -tih

It has been documented in doc/UPDATING:

+	removal of the vadvise syscall requires manual removal of all
+	associated files from the libc build object directory (including
+	the .depend files) - a command like
+		cd $OBJ && find . -type d -name libc | xargs rm -rf
+	or a one time build without -u will do.

Attachment: signature.asc
Description: OpenPGP digital signature

Home | Main Index | Thread Index | Old Index