Re: Compiling TeX Live on 10.5 (was: libatomic build failure 10.5/x86)

[Ken Cunningham]

On 2018-04-26, at 8:24 AM, Ken Cunningham wrote:
> 
> 
> well disabling luajit just leads to the same error I found when I used 
> 
> --with-system-luajit
> 
> One or two more iterations and I we should have this :>

Fixed. I'll put something up for a PR later today.

Ken

Re: Compiling TeX Live on 10.5 (was: libatomic build failure 10.5/x86)

[Ken Cunningham]

On 2018-04-26, at 7:17 AM, Ken Cunningham wrote:

> 
> On 2018-04-26, at 5:42 AM, Mojca Miklavec wrote:
> 
>>> If you use the_silver_searcher on texlive-bin you will see a flag in 
>>> autotools build scripts called need_luajit . It looks like many different 
>>> tools call for it, and you'd have to disable a lot to get past needing it.
>> 
>> I have no time to check right now, but I'm pretty sure that nothing
>> beyond luajittex and mfluajit should need it. Disabling the two should
>> really do its job.
>> 
>> Mojca
> 
> I think you're right. need_luajit pops up in a lot of places, but it 
> condenses around those two items where it does pop up. That should work.
> 
> K

well disabling luajit just leads to the same error I found when I used 

--with-system-luajit

One or two more iterations and I we should have this :>

Ken

Re: Compiling TeX Live on 10.5 (was: libatomic build failure 10.5/x86)

[Ken Cunningham]

On 2018-04-26, at 5:42 AM, Mojca Miklavec wrote:

>> If you use the_silver_searcher on texlive-bin you will see a flag in 
>> autotools build scripts called need_luajit . It looks like many different 
>> tools call for it, and you'd have to disable a lot to get past needing it.
> 
> I have no time to check right now, but I'm pretty sure that nothing
> beyond luajittex and mfluajit should need it. Disabling the two should
> really do its job.
> 
> Mojca

I think you're right. need_luajit pops up in a lot of places, but it condenses 
around those two items where it does pop up. That should work.

K


KensMacBookPro-2:texlive-source-20170604-stripped$ ag need_luajit .
autom4te.cache/output.1
4478:  need_luajit=yes
4623:  need_luajit=yes

autom4te.cache/output.2
4478:  need_luajit=yes
4623:  need_luajit=yes

configure
4478:  need_luajit=yes
4623:  need_luajit=yes

libs/autom4te.cache/output.1
3658:  need_luajit=yes
3803:  need_luajit=yes
5519:if test -x $srcdir/luajit/configure && test "x$with_system_luajit" != xyes 
&& test "x$need_luajit" = xyes; then

libs/autom4te.cache/output.2
3658:  need_luajit=yes
3803:  need_luajit=yes
5519:if test -x $srcdir/luajit/configure && test "x$with_system_luajit" != xyes 
&& test "x$need_luajit" = xyes; then

libs/configure
3658:  need_luajit=yes
3803:  need_luajit=yes
5519:if test -x $srcdir/luajit/configure && test "x$with_system_luajit" != xyes 
&& test "x$need_luajit" = xyes; then

texk/autom4te.cache/output.1
3658:  need_luajit=yes
3803:  need_luajit=yes

texk/autom4te.cache/output.2
3658:  need_luajit=yes
3803:  need_luajit=yes

texk/configure
3658:  need_luajit=yes
3803:  need_luajit=yes

texk/web2c/autom4te.cache/output.1
18793:  need_luajit=yes
18938:  need_luajit=yes

texk/web2c/autom4te.cache/output.2
18793:  need_luajit=yes
18938:  need_luajit=yes

texk/web2c/configure
18793:  need_luajit=yes
18938:  need_luajit=yes

utils/autom4te.cache/output.1
3658:  need_luajit=yes
3803:  need_luajit=yes

utils/autom4te.cache/output.2
3658:  need_luajit=yes
3803:  need_luajit=yes

utils/configure
3658:  need_luajit=yes
3803:  need_luajit=yes

Re: Compiling TeX Live on 10.5 (was: libatomic build failure 10.5/x86)

[Ken Cunningham]

> On Apr 26, 2018, at 04:19, Mojca Miklavec  wrote:
> 
>> On 26 April 2018 at 13:12, Riccardo Mottola wrote:
>>> On 2018-04-26 07:33:30 +0200 Mojca Miklavec wrote:
>>> 
>>> Riccardo, can you please try:
>>>sudo port -v build luajit configure.compiler=macports-gcc-6
>>> or
>>>sudo port -v build luajit configure.compiler=macports-gcc-7
>>> 
>>> It should potentially lead to the same issue (it doesn't fail for me
>>> on the latest 64-bit os though). It would be nice to isolate the
>>> problem and report it to GCC developers.
>> 
>> 
>> 
>> I tried both gcc 6 and ggc 7, it was very quick and succeeded without
>> errors.
> 
> Then it must be some other flag. Maybe a different version of lua or whatever.
> 
>> The issue is thus of the "embedded" luajit?
>> 
>> I wonder why --disable-luajittex was not effective
> 
> It could be for two reasons:
> - maybe --disable-mfluajit is also needed (you need to check the exact
> name, I'm not 100% sure if I spelled it correctly)
> - it could be that the configure option was not applied correctly
> 
> I suspect the first one, since mfluajit is relatively new and luajit
> build has at some point automatically been disabled on powerpc, so
> nobody actually noticed that the configure argument was not effective.
> 
> Mojca

If you use the_silver_searcher on texlive-bin you will see a flag in autotools 
build scripts called need_luajit . It looks like many different tools call for 
it, and you'd have to disable a lot to get past needing it.

Re: Compiling TeX Live on 10.5 (was: libatomic build failure 10.5/x86)

[Ken Cunningham]

installing libcxx on 10.5 requires changing the universal archs in 
macports.conf to 

i386 x86_64

make sure you port sync because I fixed an issue with libcxx recently

it will build with clang 3.4

you'll see screenfuls of macports errors .

if you get stuck I'll post up binaries for libcxx & clang-3.9 for (and any 
other explorers because it's not super easy, although it does work

think of all your're learning!

K

> On Apr 26, 2018, at 04:19, Mojca Miklavec  wrote:
> 
>> On 26 April 2018 at 13:12, Riccardo Mottola wrote:
>>> On 2018-04-26 07:33:30 +0200 Mojca Miklavec wrote:
>>> 
>>> Riccardo, can you please try:
>>>sudo port -v build luajit configure.compiler=macports-gcc-6
>>> or
>>>sudo port -v build luajit configure.compiler=macports-gcc-7
>>> 
>>> It should potentially lead to the same issue (it doesn't fail for me
>>> on the latest 64-bit os though). It would be nice to isolate the
>>> problem and report it to GCC developers.
>> 
>> 
>> 
>> I tried both gcc 6 and ggc 7, it was very quick and succeeded without
>> errors.
> 
> Then it must be some other flag. Maybe a different version of lua or whatever.
> 
>> The issue is thus of the "embedded" luajit?
>> 
>> I wonder why --disable-luajittex was not effective
> 
> It could be for two reasons:
> - maybe --disable-mfluajit is also needed (you need to check the exact
> name, I'm not 100% sure if I spelled it correctly)
> - it could be that the configure option was not applied correctly
> 
> I suspect the first one, since mfluajit is relatively new and luajit
> build has at some point automatically been disabled on powerpc, so
> nobody actually noticed that the configure argument was not effective.
> 
> Mojca

Re: Compiling TeX Live on 10.5 (was: libatomic build failure 10.5/x86)

[Mojca Miklavec]

On 26 April 2018 at 13:12, Riccardo Mottola wrote:
> On 2018-04-26 07:33:30 +0200 Mojca Miklavec wrote:
>
>> Riccardo, can you please try:
>> sudo port -v build luajit configure.compiler=macports-gcc-6
>> or
>> sudo port -v build luajit configure.compiler=macports-gcc-7
>>
>> It should potentially lead to the same issue (it doesn't fail for me
>> on the latest 64-bit os though). It would be nice to isolate the
>> problem and report it to GCC developers.
>
>
>
> I tried both gcc 6 and ggc 7, it was very quick and succeeded without
> errors.

Then it must be some other flag. Maybe a different version of lua or whatever.

> The issue is thus of the "embedded" luajit?
>
> I wonder why --disable-luajittex was not effective

It could be for two reasons:
- maybe --disable-mfluajit is also needed (you need to check the exact
name, I'm not 100% sure if I spelled it correctly)
- it could be that the configure option was not applied correctly

I suspect the first one, since mfluajit is relatively new and luajit
build has at some point automatically been disabled on powerpc, so
nobody actually noticed that the configure argument was not effective.

Mojca

Re: Compiling TeX Live on 10.5 (was: libatomic build failure 10.5/x86)

[Riccardo Mottola via macports-users]

Hi Mojca,

On 2018-04-26 07:33:30 +0200 Mojca Miklavec  wrote:


Riccardo, can you please try:
sudo port -v build luajit configure.compiler=macports-gcc-6
or
sudo port -v build luajit configure.compiler=macports-gcc-7

It should potentially lead to the same issue (it doesn't fail for me
on the latest 64-bit os though). It would be nice to isolate the
problem and report it to GCC developers.



I tried both gcc 6 and ggc 7, it was very quick and succeeded without 
errors.


The issue is thus of the "embedded" luajit?

I wonder why --disable-luajittex was not effective

Riccardo

Re: Compiling TeX Live on 10.5 (was: libatomic build failure 10.5/x86)

[Ken Cunningham]

On 2018-04-25, at 10:33 PM, Mojca Miklavec wrote:

> On 26 April 2018 at 05:38, Ken Cunningham wrote:
>>> On Apr 25, 2018, at 5:23 PM, Ken Cunningham wrote:
>>> 
>>> you know, I went back and looked at my notes.
>>> 
>>> I did in fact  build this with clang-3.4, but I overrode the cxx11 PG's 
>>> macports-libstdc++ changes to do it. It worked fine on Intel Tiger as well. 
>>> Here's the command line I used:
>>> 
>>> sudo port -v install texlive-bin configure.compiler=macports-clang-3.4 
>>> configure.cxx_stdlib=libstdc++
>>> 
>> 
>> I was hallucinating.  clang-3.9 did work on 10.5 Intel, but forcing the 
>> stdlib with clang-3.4 did not.
>> 
>> At present, I can’t build texlive-bin on 10.4 Intel. Will see what can be 
>> done about that.
> 
> Before you waste too much time on this:
> - I still claim that TeX Live 2017 should compile without C++11 by
> default when you disable dvisvgm (unless C++11 is needed because of
> dependency on icu, poppler, ... etc. which happen to need C++11 just
> because MacPorts ships the latest version of them)
> - TeX Live 2018 has basically been released, so any effort spent
> towards making TL 2017 work on those older cats should better be spent
> for the latest version
> 
> Riccardo, can you please try:
>sudo port -v build luajit configure.compiler=macports-gcc-6
> or
>sudo port -v build luajit configure.compiler=macports-gcc-7
> 
> It should potentially lead to the same issue (it doesn't fail for me
> on the latest 64-bit os though). It would be nice to isolate the
> problem and report it to GCC developers.
> 
> Mojca


you'll find luajit builds OK with gcc6 on 10.4 Intel

and there is an option to do this in texlive-bin:

--with-system-luajit

that leads to an error later on when something tries to for a rebuild the 
internal luajit for some reason, but that is easy to patch out too...

but -- drumroll -- it still errors out after that :>

Ken

Re: Compiling TeX Live on 10.5 (was: libatomic build failure 10.5/x86)

[Mojca Miklavec]

On 26 April 2018 at 05:38, Ken Cunningham wrote:
>> On Apr 25, 2018, at 5:23 PM, Ken Cunningham wrote:
>>
>> you know, I went back and looked at my notes.
>>
>> I did in fact  build this with clang-3.4, but I overrode the cxx11 PG's 
>> macports-libstdc++ changes to do it. It worked fine on Intel Tiger as well. 
>> Here's the command line I used:
>>
>> sudo port -v install texlive-bin configure.compiler=macports-clang-3.4 
>> configure.cxx_stdlib=libstdc++
>>
>
> I was hallucinating.  clang-3.9 did work on 10.5 Intel, but forcing the 
> stdlib with clang-3.4 did not.
>
> At present, I can’t build texlive-bin on 10.4 Intel. Will see what can be 
> done about that.

Before you waste too much time on this:
- I still claim that TeX Live 2017 should compile without C++11 by
default when you disable dvisvgm (unless C++11 is needed because of
dependency on icu, poppler, ... etc. which happen to need C++11 just
because MacPorts ships the latest version of them)
- TeX Live 2018 has basically been released, so any effort spent
towards making TL 2017 work on those older cats should better be spent
for the latest version

Riccardo, can you please try:
sudo port -v build luajit configure.compiler=macports-gcc-6
or
sudo port -v build luajit configure.compiler=macports-gcc-7

It should potentially lead to the same issue (it doesn't fail for me
on the latest 64-bit os though). It would be nice to isolate the
problem and report it to GCC developers.

Mojca

Re: Compiling TeX Live on 10.5 (was: libatomic build failure 10.5/x86)

[Ken Cunningham]

> On Apr 25, 2018, at 5:23 PM, Ken Cunningham  
> wrote:
> 
> you know, I went back and looked at my notes.
> 
> I did in fact  build this with clang-3.4, but I overrode the cxx11 PG's 
> macports-libstdc++ changes to do it. It worked fine on Intel Tiger as well. 
> Here's the command line I used:
> 
> sudo port -v install texlive-bin configure.compiler=macports-clang-3.4 
> configure.cxx_stdlib=libstdc++
> 

I was hallucinating.  clang-3.9 did work on 10.5 Intel, but forcing the stdlib 
with clang-3.4 did not. 

At present, I can’t build texlive-bin on 10.4 Intel. Will see what can be done 
about that.

Sorry, Ken

Re: Compiling TeX Live on 10.5 (was: libatomic build failure 10.5/x86)

[Ken Cunningham]

On 2018-04-25, at 11:42 AM, Ken Cunningham wrote:


>> Forcing clang-3.4 brings up this:
>> 
>>  /opt/local/bin/clang++-mp-3.4 -DHAVE_CONFIG_H -I.  
>> -I./TECkit-src/source/Public-headers  -DNDEBUG -isystem/opt/local/include  
>> -pipe -Os -std=c++11 -Wno-reserved-user-defined-literal 
>> -D_GLIBCXX_USE_CXX11_ABI=0 -stdlib=macports-libstdc++ -arch i386 -MT 
>> TECkit-src/source/UnicodeNames.o -MD -MP -MF $depbase.Tpo -c -o 
>> TECkit-src/source/UnicodeNames.o TECkit-src/source/UnicodeNames.cpp &&\
>>  mv -f $depbase.Tpo $depbase.Po
>> clang: error: invalid library name in argument '-stdlib=macports-libstdc++'
>> clang: error: invalid library name in argument '-stdlib=macports-libstdc++'
>> make[5]: *** [TECkit-src/source/UnicodeNames.o] Error 1
>> make[5]: *** Waiting for unfinished jobs
>> make[5]: *** [TECkit-src/source/Compiler.o] Error 1
>> make[5]: Leaving directory `/opt/local/var/macports/build/
> 

you know, I went back and looked at my notes.

I did in fact  build this with clang-3.4, but I overrode the cxx11 PG's 
macports-libstdc++ changes to do it. It worked fine on Intel Tiger as well. 
Here's the command line I used:

sudo port -v install texlive-bin configure.compiler=macports-clang-3.4 
configure.cxx_stdlib=libstdc++

Corner cases.

Ken

Re: Compiling TeX Live on 10.5 (was: libatomic build failure 10.5/x86)

[Ryan Schmidt]

On Apr 25, 2018, at 13:46, Riccardo Mottola wrote:

> I need it just as a dependency of gtk2. It is interesting that my last 
> install (just 1 or 2 months ago) did not require it!

gtk2 requires gtk-doc. When gtk-doc was updated to version 1.28 last month, 
dblatex was added as a dependency.

https://github.com/macports/macports-ports/commit/638b959cbab079501073a9f1e9d3e931844e8c97

dblatex requires texlive.

Re: Compiling TeX Live on 10.5 (was: libatomic build failure 10.5/x86)

[Riccardo Mottola via macports-users]

Hi Mojca,

On 2018-04-25 11:05:31 +0200 Mojca Miklavec  wrote:

I cannot say why this breaks. This gcc 6 compiler is selected because 
of

PortGroup cxx11 1.1
but as far as I remember only dvisvgm required C++11 and that one is
packaged as a separate port anyway. You could try building with gcc 7
(in case it "helps", I tried to build TeX Live 2018 on 10.5/PPC and
that one failed due to another compiler error).

Last year I was able to compile TeX Live 2017 (outside of MacPorts) on
10.6 with gcc 4.2 against 10.5 SDK (after disabling dvisvgm build).


I need it just as a dependency of gtk2. It is interesting that my last 
install (just 1 or 2 months ago) did not require it!



But TeX Live 2018 requires C++11 anyway (ok, maybe it only does so
because of ICU, poppler etc., and the rest of the sources would still
compile without it), so you would soon run into the same compiler
problem.


Maybe we can disable it in gtk2 for old OS's?


As a quick fix, I would suggest you to pass the
--disable-luajittex
flag. Again, I'm not sure why this would be needed, it should
theoretically work (I have a working luajittex for 10.5/i386), but
that might be the fastest workaround. I'm pretty sure you don't need
that binary there.

That's already the case for PPC:

https://github.com/macports/macports-ports/blob/master/tex/texlive-bin/Portfile#L199

If this is in fact broken for some weird reason, we should at least:
- disable luajit in texlive-bin for 10.5/i386 (maybe do more testing)
- test whether gcc 7/8 has the same issue and potentially report it 
upstream


as a "quick fix" I just edited the Portfile

/opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/tex/texlive-bin

and added

--disable-luajittex \

to configure.args

Is that fine? because even after cleaning the build fails stubbornly 
in the same place in LuaJIT!


Riccardo

Re: Compiling TeX Live on 10.5 (was: libatomic build failure 10.5/x86)

[Ken Cunningham]

On 2018-04-25, at 11:38 AM, Riccardo Mottola wrote:

> Hi,

> Forcing clang-3.4 brings up this:
> 
>   /opt/local/bin/clang++-mp-3.4 -DHAVE_CONFIG_H -I.  
> -I./TECkit-src/source/Public-headers  -DNDEBUG -isystem/opt/local/include  
> -pipe -Os -std=c++11 -Wno-reserved-user-defined-literal 
> -D_GLIBCXX_USE_CXX11_ABI=0 -stdlib=macports-libstdc++ -arch i386 -MT 
> TECkit-src/source/UnicodeNames.o -MD -MP -MF $depbase.Tpo -c -o 
> TECkit-src/source/UnicodeNames.o TECkit-src/source/UnicodeNames.cpp &&\
>   mv -f $depbase.Tpo $depbase.Po
> clang: error: invalid library name in argument '-stdlib=macports-libstdc++'
> clang: error: invalid library name in argument '-stdlib=macports-libstdc++'
> make[5]: *** [TECkit-src/source/UnicodeNames.o] Error 1
> make[5]: *** Waiting for unfinished jobs
> make[5]: *** [TECkit-src/source/Compiler.o] Error 1
> make[5]: Leaving directory `/opt/local/var/macports/build/


Oh, yes, I saw that too now that you mention it.

> '-stdlib=macports-libstdc++

is a rather fancy MacPorts-only addition to clang 3.9+ that allows fancy 
footwork with the c++ standard library. It gets added by the cxx11 PortGroup. 
For that to work, you need clang-3.9. (although I have it working with 
clang-3.8 myself, on PPC no less -- but that is another story).

> 
> Perhaps that is why you selected gcc6, due to libstdc++
> Should I try installing clang 3.9, if it it works on 10.5?

clang-3.9 does work on 10.5, and works very well for me.

Ken

Re: Compiling TeX Live on 10.5 (was: libatomic build failure 10.5/x86)

[Riccardo Mottola via macports-users]

Hi,


On 2018-04-25 20:11:32 +0200 Ken Cunningham 
 wrote:




But you have to be very facile at forcing different compilers as I 
showed you.
A very great amount of software no longer builds with MacPorts 
default 
compilers on these old systems, and you have to try different ones.  
Don't 
have any expectations that things will go smoothly for updates. There 
are 
only a half-dozen of us who work on this, or less, and many ports may 
not 
have been tested.


No worries :) just forced them, I was asking and read the whole thread 
before working.




gcc6 and clang-3.x are usually your go-to compilers when the default 
doesn't 
work.


Yes of course, I already have them, I also gave gcc7.

Forcing gcc7 doesn't help mutch:

ibtool: compile:  /opt/local/bin/gcc-mp-7 -DHAVE_CONFIG_H -I. 
-I./LuaJIT-src/src -DLUAJIT_ENABLE_LUA52COMPAT -DLUAI_HASHLIMIT=6 
-U_FORTIFY_SOURCE -isystem/opt/local/include -fomit-frame-pointer 
-march=i686 -msse -msse2 -mfpmath=sse -fno-stack-protector -Wall -pipe 
-Os -m32 -MT LuaJIT-src/src/lj_cconv.lo -MD -MP -MF 
LuaJIT-src/src/.deps/lj_cconv.Tpo -c LuaJIT-src/src/lj_cconv.c  
-fno-common -DPIC -o LuaJIT-src/src/.libs/lj_cconv.o
depbase=`echo LuaJIT-src/src/lj_cdata.lo | sed 
's|[^/]*$|.deps/&|;s|\.lo$||'`;\
	/bin/sh ./libtool  --tag=CC   --mode=compile /opt/local/bin/gcc-mp-7 
-DHAVE_CONFIG_H -I.  -I./LuaJIT-src/src -DLUAJIT_ENABLE_LUA52COMPAT 
-DLUAI_HASHLIMIT=6 -U_FORTIFY_SOURCE -isystem/opt/local/include 
-fomit-frame-pointer -march=i686 -msse -msse2 -mfpmath=sse 
-fno-stack-protector  -Wall -pipe -Os -m32 -MT 
LuaJIT-src/src/lj_cdata.lo -MD -MP -MF $depbase.Tpo -c -o 
LuaJIT-src/src/lj_cdata.lo LuaJIT-src/src/lj_cdata.c &&\

mv -f $depbase.Tpo $depbase.Plo
LuaJIT-src/src/lj_cconv.c: In function 'lj_cconv_ct_ct':
LuaJIT-src/src/lj_cconv.c:368:1: internal compiler error: in 
gen_reg_rtx, at emit-rtl.c:1026

 }
 ^

Another compiler error!

Forcing clang-3.4 brings up this:

	/opt/local/bin/clang++-mp-3.4 -DHAVE_CONFIG_H -I.  
-I./TECkit-src/source/Public-headers  -DNDEBUG 
-isystem/opt/local/include  -pipe -Os -std=c++11 
-Wno-reserved-user-defined-literal -D_GLIBCXX_USE_CXX11_ABI=0 
-stdlib=macports-libstdc++ -arch i386 -MT 
TECkit-src/source/UnicodeNames.o -MD -MP -MF $depbase.Tpo -c -o 
TECkit-src/source/UnicodeNames.o TECkit-src/source/UnicodeNames.cpp 
&&\

mv -f $depbase.Tpo $depbase.Po
clang: error: invalid library name in argument 
'-stdlib=macports-libstdc++'
clang: error: invalid library name in argument 
'-stdlib=macports-libstdc++'

make[5]: *** [TECkit-src/source/UnicodeNames.o] Error 1
make[5]: *** Waiting for unfinished jobs
make[5]: *** [TECkit-src/source/Compiler.o] Error 1
make[5]: Leaving directory `/opt/local/var/macports/build/

Perhaps that is why you selected gcc6, due to libstdc++
Should I try installing clang 3.9, if it it works on 10.5?


We appreciate the help!!


And I appreciate yours.

Riccardo

Re: Compiling TeX Live on 10.5 (was: libatomic build failure 10.5/x86)

[Ken Cunningham]

On 2018-04-25, at 10:59 AM, Riccardo Mottola wrote:

> Hi,
> 
> Michael Dickens wrote:
>> That said, on 10.6 Intel there's an issue with objc++ compiling, where the 
>> OBJCXXFLAGS requires "-fpermissive" to get over some untyped enum issues in 
>> some security framework. I had 'port' use the defaults for compiler & other 
>> settings, and with a small tweak to the Portfile the port builds correctly 
>> now. I'll do a PR for this fix soon-ish. Maybe this is the issue with GCC6?
> 
> maybe, but it shouldn't spit out a "internal compiler error" but a 
> warning/error I suppose?

That's an unexpected gcc error, I guess. Maybe they've covered it off in gcc7 
or newer. If not, should be a gcc ticket.


> 
> I'm still curious why it selects gcc6 when the port has other "preferred 
> compilers" installed.

MacPorts has a list of preferred compilers, usually the ones already in 
installed on a system by Xcode.

Then there are additions to that by us, for compilers we want used next, 
depending on the system (gcc6 for PPC, clang-3.4 for Intel, for example). There 
is debate about what these should be, but we try to make smart choices. Then 
there are fallback compilers, that can be called in.

MacPorts makes a list of these compilers, in order. Then it looks at what 
compilers have been "blacklisted" in the Portfile as known not to work.

It chooses the first one on the list that is not blacklisted.



> 
> I will try with gcc7 and clang and then in casse Mojca's suggestion.

That works! in my experience, gcc6 on PPC usually works if the defaults don't.

clang-3.x usually works on Intel if the defaults done.


For 10.5 Intel, clang-3.9 is fantastic, and can build almost anything. That's 
what I use when the defaults don't work. But it's a bit of work to get it 
installed.

K

Re: Compiling TeX Live on 10.5 (was: libatomic build failure 10.5/x86)

[Ken Cunningham]

On 2018-04-25, at 10:59 AM, Riccardo Mottola wrote:

> Hi,
> 
> Michael Dickens wrote:
>> That said, on 10.6 Intel there's an issue with objc++ compiling, where the 
>> OBJCXXFLAGS requires "-fpermissive" to get over some untyped enum issues in 
>> some security framework. I had 'port' use the defaults for compiler & other 
>> settings, and with a small tweak to the Portfile the port builds correctly 
>> now. I'll do a PR for this fix soon-ish. Maybe this is the issue with GCC6?
> 
> maybe, but it shouldn't spit out a "internal compiler error" but a 
> warning/error I suppose?
> 
> I'm still curious why it selects gcc6 when the port has other "preferred 
> compilers" installed.
> 
> I will try with gcc7 and clang and then in casse Mojca's suggestion.
> 
> Riccardo

If you're going to help out with keeping older systems alive in MacPorts, that 
would be great. I can bring you up to speed on how MacPorts works behind the 
scenes.

But you have to be very facile at forcing different compilers as I showed you. 

A very great amount of software no longer builds with MacPorts default 
compilers on these old systems, and you have to try different ones.  Don't have 
any expectations that things will go smoothly for updates. There are only a 
half-dozen of us who work on this, or less, and many ports may not have been 
tested.

gcc6 and clang-3.x are usually your go-to compilers when the default doesn't 
work.



We appreciate the help!!

Ken

Re: Compiling TeX Live on 10.5 (was: libatomic build failure 10.5/x86)

[Riccardo Mottola via macports-users]

Hi,

Michael Dickens wrote:

That said, on 10.6 Intel there's an issue with objc++ compiling, where the OBJCXXFLAGS 
requires "-fpermissive" to get over some untyped enum issues in some security 
framework. I had 'port' use the defaults for compiler & other settings, and with a small 
tweak to the Portfile the port builds correctly now. I'll do a PR for this fix soon-ish. 
Maybe this is the issue with GCC6?


maybe, but it shouldn't spit out a "internal compiler error" but a 
warning/error I suppose?


I'm still curious why it selects gcc6 when the port has other "preferred 
compilers" installed.


I will try with gcc7 and clang and then in casse Mojca's suggestion.

Riccardo

Re: Compiling TeX Live on 10.5 (was: libatomic build failure 10.5/x86)

[Ken Cunningham]

> On Apr 25, 2018, at 08:30, Mojca Miklavec  wrote:
> 
>> On 25 April 2018 at 16:37, Michael Dickens wrote:
>> I don't think I did anything special, and texlive-bin installed for me on 
>> 10.5 PPC without complaint.
> 
> But note that the code which failed for Riccardo is disabled on PPC.


yes, I should have said I used clang 3.4 on 10.5 Intel. On PPC gcc6 indeed 
works. 

There are lots of these minor hiccups on old systems, easy to get around but 
hiccups. Often I fix them and put the fix in LeopardPorts or TigerPorts quickly 
for me at least to use. I post them up to MacPorts if I get them to a point 
where I think they'll be accepted...

K


> 
>> Maybe this is the issue with GCC6?
> 
> Almost definitely.
> 
> Mojca

Re: Compiling TeX Live on 10.5 (was: libatomic build failure 10.5/x86)

[Mojca Miklavec]

On 25 April 2018 at 16:37, Michael Dickens wrote:
> I don't think I did anything special, and texlive-bin installed for me on 
> 10.5 PPC without complaint.

But note that the code which failed for Riccardo is disabled on PPC.

> Maybe this is the issue with GCC6?

Almost definitely.

Mojca

Re: Compiling TeX Live on 10.5 (was: libatomic build failure 10.5/x86)

[Ken Cunningham]

for texlive-bin on 10.5, I built it with clang 3.4 with success.

sudo port clean texlive-bin
sudo port -v install texlive-bin configure.compiler=macports-clang-3.4

I forget just now why gcc6 failed.
K

> On Apr 25, 2018, at 02:05, Mojca Miklavec  wrote:
> 
> Hi,
> 
> I cannot say why this breaks. This gcc 6 compiler is selected because of
>PortGroup cxx11 1.1
> but as far as I remember only dvisvgm required C++11 and that one is
> packaged as a separate port anyway. You could try building with gcc 7
> (in case it "helps", I tried to build TeX Live 2018 on 10.5/PPC and
> that one failed due to another compiler error).
> 
> Last year I was able to compile TeX Live 2017 (outside of MacPorts) on
> 10.6 with gcc 4.2 against 10.5 SDK (after disabling dvisvgm build).
> 
> But TeX Live 2018 requires C++11 anyway (ok, maybe it only does so
> because of ICU, poppler etc., and the rest of the sources would still
> compile without it), so you would soon run into the same compiler
> problem.
> 
> As a quick fix, I would suggest you to pass the
>--disable-luajittex
> flag. Again, I'm not sure why this would be needed, it should
> theoretically work (I have a working luajittex for 10.5/i386), but
> that might be the fastest workaround. I'm pretty sure you don't need
> that binary there.
> 
> That's already the case for PPC:
> 
> https://github.com/macports/macports-ports/blob/master/tex/texlive-bin/Portfile#L199
> 
> If this is in fact broken for some weird reason, we should at least:
> - disable luajit in texlive-bin for 10.5/i386 (maybe do more testing)
> - test whether gcc 7/8 has the same issue and potentially report it upstream
> 
> Mojca
> 
>> On 25 April 2018 at 10:46, Riccardo Mottola via macports-users wrote:
>> 
>> Then I resume upgrading..  and something pulls in texlive-bin
>> 
>> --->  Computing dependencies for texlive-bin
>> --->  Building texlive-bin
>> Error: Failed to build texlive-bin: command execution failed
>> Error: See
>> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_tex_texlive-bin/texlive-bin/main.log
>> for details.
>> Error: Problem while installing texlive-bin
>> 
>> I do not have it currently installed:
>> 
>>  texinfo @6.5_1 (active)
>>  texlive-common @2017.1_0 (active)
>> 
>> 
>> so it is not an upgraded but a new dependency?
>> 
>> The error is an interna compiler error, not very reassuring!
>> 
>> :info:build make[4]: Entering directory
>> `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_tex_texlive-bin/texlive-bin/work/texlive-source-20170604-stripped/libs/luajit'
>> :info:build depbase=`echo LuaJIT-src/src/lj_cconv.lo | sed
>> 's|[^/]*$|.deps/&|;s|\.lo$||'`;\
>> :info:build /bin/sh ./libtool  --tag=CC   --mode=compile
>> /opt/local/bin/gcc-mp-6 -DHAVE_CONFIG_H -I.  -I./LuaJIT-src/src
>> -DLUAJIT_ENABLE_LUA52COMPAT -DLUAI_HASHLIMIT=6 -U_FORTIFY_SOURCE
>> -isystem/opt/local/include -fomit-frame-pointer -march=i686 -msse -msse2
>> -mfpmath=sse -fno-stack-protector  -Wall -pipe -Os -m32 -MT
>> LuaJIT-src/src/lj_cconv.lo -MD -MP -MF $depbase.Tpo -c -o
>> LuaJIT-src/src/lj_cconv.lo LuaJIT-src/src/lj_cconv.c &&\
>> :info:build mv -f $depbase.Tpo $depbase.Plo
>> :info:build depbase=`echo LuaJIT-src/src/lj_ctype.lo | sed
>> 's|[^/]*$|.deps/&|;s|\.lo$||'`;\
>> :info:build /bin/sh ./libtool  --tag=CC   --mode=compile
>> /opt/local/bin/gcc-mp-6 -DHAVE_CONFIG_H -I.  -I./LuaJIT-src/src
>> -DLUAJIT_ENABLE_LUA52COMPAT -DLUAI_HASHLIMIT=6 -U_FORTIFY_SOURCE
>> -isystem/opt/local/include -fomit-frame-pointer -march=i686 -msse -msse2
>> -mfpmath=sse -fno-stack-protector  -Wall -pipe -Os -m32 -MT
>> LuaJIT-src/src/lj_ctype.lo -MD -MP -MF $depbase.Tpo -c -o
>> LuaJIT-src/src/lj_ctype.lo LuaJIT-src/src/lj_ctype.c &&\
>> :info:build mv -f $depbase.Tpo $depbase.Plo
>> :info:build libtool: compile:  /opt/local/bin/gcc-mp-6 -DHAVE_CONFIG_H -I.
>> -I./LuaJIT-src/src -DLUAJIT_ENABLE_LUA52COMPAT -DLUAI_HASHLIMIT=6
>> -U_FORTIFY_SOURCE -isystem/opt/local/include -fomit-frame-pointer
>> -march=i686 -msse -msse2 -mfpmath=sse -fno-stack-protector -Wall -pipe -Os
>> -m32 -MT LuaJIT-src/src/lj_ctype.lo -MD -MP -MF
>> LuaJIT-src/src/.deps/lj_ctype.Tpo -c LuaJIT-src/src/lj_ctype.c  -fno-common
>> -DPIC -o LuaJIT-src/src/.libs/lj_ctype.o
>> :info:build libtool: compile:  /opt/local/bin/gcc-mp-6 -DHAVE_CONFIG_H -I.
>> -I./LuaJIT-src/src -DLUAJIT_ENABLE_LUA52COMPAT -DLUAI_HASHLIMIT=6
>> -U_FORTIFY_SOURCE -isystem/opt/local/include -fomit-frame-pointer
>> -march=i686 -msse -msse2 -mfpmath=sse -fno-stack-protector -Wall -pipe -Os
>> -m32 -MT LuaJIT-src/src/lj_cconv.lo -MD -MP -MF
>> LuaJIT-src/src/.deps/lj_cconv.Tpo -c LuaJIT-src/src/lj_cconv.c  -fno-common
>> -DPIC -o LuaJIT-src/src/.libs/lj_cconv.o
>> :info:build LuaJIT-src/src/lj_cconv.c: In function 'lj_cconv_ct_ct':
>> :info:build LuaJIT-src/src/lj_cconv.c:368:1: internal compiler error: in
>>