Bug 193289 - print/texlive-base fails to build on powerpc64
Summary: print/texlive-base fails to build on powerpc64
Status: Closed Feedback Timeout
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: powerpc Any
: --- Affects Some People
Assignee: Hiroki Sato
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-03 16:39 UTC by Justin Hibbits
Modified: 2016-01-17 15:14 UTC (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Justin Hibbits freebsd_committer freebsd_triage 2014-09-03 16:39:22 UTC
texlive-base by default builds luajit, which doesn't currently support powerpc64.  Adding --disable-luajit to the configure args should fix this (conditional on the architecture).
Comment 1 Tilman Keskinoz freebsd_committer freebsd_triage 2014-09-03 20:44:01 UTC
over to maintainer
Comment 2 Justin Hibbits freebsd_committer freebsd_triage 2014-09-05 20:13:28 UTC
(In reply to Justin Hibbits from comment #0)
> texlive-base by default builds luajit, which doesn't currently support
> powerpc64.  Adding --disable-luajit to the configure args should fix this
> (conditional on the architecture).

I'm wrong on this (was going by comments made on RedHat's bugzilla regarding this), simply adding --disable-luajit doesn't cause it to not build luajit.
Comment 3 Justin Hibbits freebsd_committer freebsd_triage 2014-09-22 19:43:58 UTC
The correct argument to pass is '--disable-luajittex'.  It passes a build in poudriere by adding that argument to CONFIGURE_ARGS.
Comment 4 RoadK1LL 2014-10-18 19:14:03 UTC
This appears to have fixed the problem. Adding --disable-luajittex to the MakeFile allowed it to finish building via source.

I did do a portsnap fetch update 10 minutes before going here to see if there was a known problem. So it appears that the fix has not made its way down the line to FreeBSD 10.0-RELEASE (r260789) on generic PPC64.
Comment 5 RoadK1LL 2014-10-18 19:14:51 UTC
I also had to add:
"MAKE_JOBS_UNSAFE=yes.