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
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
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
> 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
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 &
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
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
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
>>>
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
> 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.
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
>>
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.
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
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
>
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
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
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
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
> 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
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
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
21 matches
Mail list logo