Bug 1316904 - Disable luajit on MIPS
Summary: Disable luajit on MIPS
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: texlive
Version: rawhide
Hardware: mips64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Tom "spot" Callaway
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1322530 (view as bug list)
Depends On:
Blocks: MIPS
TreeView+ depends on / blocked
 
Reported: 2016-03-11 12:39 UTC by Michal Toman
Modified: 2017-02-20 21:44 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-20 21:44:38 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Disable-luajit-on-MIPS.patch (2.50 KB, patch)
2016-03-11 12:39 UTC, Michal Toman
no flags Details | Diff
Disable-luajit-on-MIPS.patch (3.45 KB, patch)
2016-08-14 16:04 UTC, Michal Toman
no flags Details | Diff

Description Michal Toman 2016-03-11 12:39:54 UTC
Created attachment 1135218 [details]
Disable-luajit-on-MIPS.patch

Description of problem:
We are trying to bring Fedora to MIPS platform and this requires disabling luajit in texlive. There is no luajit for MIPS.

Actual results:
texlive tries to build with luajit and fails

Expected results:
texlive does not build luajit

Additional info:
Attaching dist-git patch. It would be great if this could also be applied to F24.

Comment 1 Michal Toman 2016-04-27 16:51:02 UTC
*** Bug 1322530 has been marked as a duplicate of this bug. ***

Comment 2 Jan Kurik 2016-07-26 05:07:11 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle.
Changing version to '25'.

Comment 3 Michal Toman 2016-08-14 16:04:37 UTC
Created attachment 1190772 [details]
Disable-luajit-on-MIPS.patch

Still valid, updated for current rawhide. It would be nice to have this in F25 as well.

Comment 4 Tom "spot" Callaway 2016-08-15 14:01:35 UTC
This will show up when I finally manage to beat the texlive update into submission.

Comment 5 Tom "spot" Callaway 2017-02-20 21:44:38 UTC
This has been fixed since 5:2016-2.20160520.


Note You need to log in before you can comment on or make changes to this bug.