Bug 218183 - graphics/jpeg-turbo: Linker error "* expected, but got jsimd_*" for aarch64
Summary: graphics/jpeg-turbo: Linker error "* expected, but got jsimd_*" for aarch64
Status: Closed Not Enough Information
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: arm64 Any
: --- Affects Only Me
Assignee: Port Management Team
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-28 10:15 UTC by Simon Rozman
Modified: 2017-03-31 21:00 UTC (History)
0 users

See Also:
bugzilla: maintainer-feedback? (portmgr)

Attachments
Poudriere log (46.96 KB, text/plain)
2017-03-28 10:15 UTC, Simon Rozman 		no flags Details
make build log (50.68 KB, text/plain)
2017-03-28 19:15 UTC, Simon Rozman 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Simon Rozman 2017-03-28 10:15:53 UTC 
Created attachment 181264 [details]
Poudriere log

I am trying to compile the graphics/jpeg-turbo for ARM64 (aarch64) using Poudriere (cross-compiling on amd64).

The log is attached.

Host computer:
- FreeBSD 12.0-CURRENT r315864.
- /usr/ports r436962 (devel/binutils, devel/aarch64, devel/aarch64-none-elf-binutils, devel/arm-gnueabi-binutils, and devel/arm-none-eabi-binutil are pinned to r436731, see: https://www.mail-archive.com/freebsd-ports@freebsd.org/msg73448.html)

Poudriere aarch64 jail:
- FreeBSD 12.0-CURRENT r313109
- /usr/ports r437014 (devel/binutils and others pinned to r436731 for the same reason as on the host computer)
Comment 1 Antoine Brodin freebsd_committer freebsd_triage 2017-03-28 11:36:03 UTC 
Native build works fine.
Comment 2 Simon Rozman 2017-03-28 19:15:07 UTC 
Created attachment 181278 [details]
make build log
Comment 3 Simon Rozman 2017-03-28 19:29:26 UTC 
Unfortunately "make build" on the target aarch64 system repeats the same error (see "make build log" attachment). Well, if it wouldn't, it would indicate the qemu and Poudriere problem.

The target system was booted using the same FreeBSD "world" as it was used initially by Poudriere jail. I used the same port tree and tried to build the graphics/jpeg-turbo on the target system.

What revision of 12.0-CURRENT aarch64 and ports tree are you testing on, should we synchronise to the same version first?

I cannot use the head for ports tree, as it has broken aarch64-binutils (rendering crochet make buildworld fail).
I cannot use the head for FreeBSD, as it does not work on my test aarch64 system (Raspberry Pi 3) anymore.
Comment 4 Antoine Brodin freebsd_committer freebsd_triage 2017-03-28 20:55:11 UTC 
(In reply to Simon Rozman from comment #3)
we are testing on 11.0-RELEASE,  both ports/head and ports/quarterly
Comment 5 Simon Rozman 2017-03-31 21:00:43 UTC 
11.0-RELEASE does not support my aarch64 system (Raspberry Pi 3).

devel/aarch64-binutils of ports/head is broken. I can't cross compile "make buildworld". If I revert it, the 11.0-RELEASE does compile, but the compiler from FreeBSD image is broken. Rendering the emulated aarch64 jail incapable of compiling ports.

If I use ports/quarterly, u-boot lacks support for RPi3.

Therefore, I can not synchronise my environment to yours.

It smells like compiler/linker problem.

May I suggest we wait until FreeBSD support for Raspberry Pi 3 improves and the dust with 12.0-CURRENT settles down a bit. Shall we mark this issue as "Closed" now and get back when all the fuss around compiler is resolved if necessary?