Summary: | app-text/texlive-core-2014-r2 on ABI=x32 - Error: pointer size mismatch in cross-build | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Bertrand Jacquin <bertrand> |
Component: | Current packages | Assignee: | Alexis Ballier <aballier> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | bertrand, josh.parsons, tex |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 393673 | ||
Attachments: |
build.log
emerge --info make luajittex controlled by a useflag modify texlive-module.eclass to not use non-existent engines |
Description
Bertrand Jacquin
2015-03-09 01:37:59 UTC
Created attachment 398450 [details]
build.log
Created attachment 398452 [details]
emerge --info
I also have this problem. The embedded luajit assumes that pointers on amd64 are 64bit. Here is the debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752041 Solution is to pass --disable-luajittex to configure on x32 builds. Created attachment 407366 [details, diff]
make luajittex controlled by a useflag
This patch adds a luajittex useflag to texlive-core, which controls whether luajittex is built. Should be usemasked on x32 profiles.
texlive-module.class also needs changes so that other texlive modules don't try to use luajittex disabling luajittex wont work since tl-basic & tl-latex both hard depend on it... Created attachment 407372 [details, diff]
modify texlive-module.eclass to not use non-existent engines
With this in conjunction with my previous patch, I can now build a complete texlive on x32.
(In reply to Alexis Ballier from comment #6) > disabling luajittex wont work since tl-basic & tl-latex both hard depend on > it... Thanks, I noticed that shortly after posting the patch... my patch to texlive-module.eclass fixes that. (In reply to Josh Parsons from comment #7) > Created attachment 407372 [details, diff] [details, diff] > modify texlive-module.eclass to not use non-existent engines This isnt good since this introduces some sort of automagic: Imagine I install tl-core with USE=-luajittex, then how can I know what I need to rebuild in order to get luajittex working? Let's see if we can get something good, scalable and maintainable: What I was thinking is adding a new 'input' variable in texlive-module.eclass, say 'TEXLIVE_MODULE_OPTIONAL_ENGINE', which would add these to IUSE (default enabled), add the usedep on tl-core and disable said engines when the useflag is disabled. A bit like what you're proposing, except controlled by an useflag instead of guessing what's in PATH or not. (In reply to Alexis Ballier from comment #9) > (In reply to Josh Parsons from comment #7) > > Created attachment 407372 [details, diff] [details, diff] [details, diff] > > modify texlive-module.eclass to not use non-existent engines > > This isnt good since this introduces some sort of automagic: > Imagine I install tl-core with USE=-luajittex, then how can I know what I > need to rebuild in order to get luajittex working? > > > Let's see if we can get something good, scalable and maintainable: > What I was thinking is adding a new 'input' variable in > texlive-module.eclass, say 'TEXLIVE_MODULE_OPTIONAL_ENGINE', which would add > these to IUSE (default enabled), add the usedep on tl-core and disable said > engines when the useflag is disabled. A bit like what you're proposing, > except controlled by an useflag instead of guessing what's in PATH or not. did that; it was simpler than what i thought; now there's luajittex useflag that can be masked on relevant profiles (please fill a bug for the x32 team for that) |