mips.mips64elhf and mips.mips64el buildworld

[Dimitry Andric]

On 4 Apr 2018, at 04:37, Cy Schubert <Cy.Schubert at cschubert.com> wrote:
> 
> Building world within the krb5 project branch after having made heimdal
> private, as of LLVM 6 the following errors are produced

Since mips is built with gcc (still), this hasn't got anything to do
with clang. :)


> /scratch/tmp/cy/obj/home/cy/projects/pvt/mips.mips64elhf/obj-lib32/tmp/u
> sr/lib32
> /libprivateasn1.so: could not read symbols: File in wrong format
> 
> and
> 
> /scratch/tmp/cy/obj/home/cy/projects/pvt/mips.mips64el/obj-lib32/tmp/usr
> /lib32/l
> ibprivateasn1.so: could not read symbols: File in wrong format
> 
> File reports,
> 
> universe12b$ file /scratch/tmp/cy/obj/home/cy/projects/pvt/mips.mips64el
> hf/obj-lib32/tmp/usr/lib32/libprivateasn1.so.11
> /scratch/tmp/cy/obj/home/cy/projects/pvt/mips.mips64elhf/obj-lib32/tmp/u
> sr/lib32/libprivateasn1.so.11: ELF 32-bit MSB shared object, MIPS,
> MIPS-III version 1 (FreeBSD), dynamically linked, not stripped
> universe12b$
> 
> Similarly for mips64el.
> 
> All other architectures built successfully.
> 
> For the stupid question: AFAICT the files are correct. Does anyone have
> any ideas?

Which program is producing the "could not read symbols" output?  The
linker?  Maybe it trips up over these 32-bit shared libraries.

It would probably help a bit if you posted the buildworld output
somewhere, so it is more easily visible how the libraries are built,
and by which program(s) they are processed.

-Dimitry

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 223 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20180404/adaf1139/attachment.sig>