> On Nov 17, 2018, at 10:03, Uli Wienands æwrote:
> Well, some progress: I was able to get over the hump by not updating all
> dependencies (-n switch),
That is not a good idea. You can end up with ports in a broken state. However,
rev-upgrade should fix that, if so.
The PR I submitted has
Well, some progress: I was able to get over the hump by not updating all
dependencies (-n switch), given that I actually have older versions of
e.g. zstd and libtiff already installed. Much to my amazement gimp2
actually built. And it even runs, albeit complaining bitterly about tiff
being out
On Nov 15, 2018, at 19:14, Riccardo Mottola wrote:
> Hi,
>
> as you thought, it is specific ASM stuff, so the typos are relative to a
> precise architecture only,
>
> On 2018-11-14 20:55:58 +0100 Ryan Schmidt wrote:
>
>> On Nov 14, 2018, at 11:17, Riccardo Mottola wrote:
>>> I wonder if thi
Hi,
as you thought, it is specific ASM stuff, so the typos are relative to
a precise architecture only,
On 2018-11-14 20:55:58 +0100 Ryan Schmidt
wrote:
On Nov 14, 2018, at 11:17, Riccardo Mottola wrote:
I wonder if this will cause issues on my 10.5 at the next upgrade,
since it
is 3
Hi,
I just run update on my box...
On 2018-11-14 20:55:58 +0100 Ryan Schmidt
wrote:
On Nov 14, 2018, at 11:17, Riccardo Mottola wrote:
I wonder if this will cause issues on my 10.5 at the next upgrade,
since it
is 32bit form me.. I'll see.
zstd and tiff built successfully on our 10.5
Ryan, thanks much. While I have not conscientiously installed with universal, I
may well have installed 32-bit programs. I’ll do as you say below when I get
back to this, hopefully this evening.
Uli
> On Nov 14, 2018, at 2:05 PM, Ryan Schmidt wrote:
>
> On Nov 14, 2018, at 11:26, Ulrich Wiena
On Nov 14, 2018, at 11:26, Ulrich Wienands wrote:
> On Nov 14, 2018, at 12:31 AM, Ryan Schmidt wrote:
>
>> On Nov 13, 2018, at 20:33, Uli Wienands wrote:
>>
>>> Ok, so I did upgrade tk. That went ok, sort of. In the process of upgrading
>>> tk it butchered several other ports ("found 61 broken
On Nov 14, 2018, at 11:17, Riccardo Mottola wrote:
> I wonder if this will cause issues on my 10.5 at the next upgrade, since it
> is 32bit form me.. I'll see.
zstd and tiff built successfully on our 10.5 PowerPC builder. The problem may
be specific to 32-bit Intel, or it may be specific to
On 2018-11-14, at 9:29 AM, Riccardo Mottola wrote:
>
> You still keep XCode's compiler, MacPorts gives you added compilers for
> compiling stuff which can be useful! Why do you worry?
> MacPorts compiler can also compile MacOS GUI stuff - up to a certain point
> when the compiler is too new an
Hi Uli,
Uli Wienands wrote:
At present I have clang 3.4, 3.7 and 5.0 installed. Don't know why not
3.9 but then, none of these were deliberately installed anyway, all
pulled in as dependencies. But I gather from the file you reference
below this is not enough. In fact, it seems like to follo
Hmm… I did not specify +universal; I don’t need that.
Do I “sudo port install gimp2 -universal” (minus universal) to suppress the
apparent default?
Uli
> On Nov 14, 2018, at 12:31 AM, Ryan Schmidt wrote:
>
>
>
> On Nov 13, 2018, at 20:33, Uli Wienands wrote:
>
>> Ok, so I did upgrade tk. Th
Hi!
Ryan Schmidt wrote:
zstd is a new dependency of the tiff port as of version 4.0.10. It's optional,
but I decided to enable it always, for simplicity. If this causes problems, we
can change tiff's zstd support to a variant.
The log shows you're building universal on 10.6. That (specificall
On Wed, 14 Nov 2018 at 10:30, Chris Jones wrote:
> On 14/11/18 02:33, Uli Wienands wrote:
> > Ok, so I did upgrade tk. That went ok, sort of. In the process of
> > upgrading tk it butchered several other ports ("found 61 broken files, 5
> > broken ports"). In the process of fixing those it ran agro
On 14/11/18 02:33, Uli Wienands wrote:
Ok, so I did upgrade tk. That went ok, sort of. In the process of
upgrading tk it butchered several other ports ("found 61 broken files, 5
broken ports"). In the process of fixing those it ran aground trying to
install zstd. As a result, my octave 4.2.1
On Nov 13, 2018, at 20:33, Uli Wienands wrote:
> Ok, so I did upgrade tk. That went ok, sort of. In the process of upgrading
> tk it butchered several other ports ("found 61 broken files, 5 broken
> ports"). In the process of fixing those it ran aground trying to install
> zstd. As a result,
> On Nov 13, 2018, at 6:33 PM, Uli Wienands wrote:
>
> it ran aground trying to install zstd.
A little prospecting shows that the tiff port was recently updated to include
zstd support
https://github.com/macports/macports-ports/commit/c4b50f5d455c061ebf22697a4e4a5a083cff43f8#diff-106d68a6f
Ken, thanks much. This looks quite attractive.
At present I have clang 3.4, 3.7 and 5.0 installed. Don't know why not
3.9 but then, none of these were deliberately installed anyway, all
pulled in as dependencies. But I gather from the file you reference
below this is not enough. In fact, it se
> On Nov 13, 2018, at 7:40 PM, Ken Cunningham
> wrote:
>
> Abandon 2004!
>
OK. You might want to know what I mean by that.
Snow Leopard can build and run a very great amount of current software. But you
need to use a newer compiler and stdlib setup to make that work smoothly.
I suggest
Probably same deal. Compiler is too old.
This ancient relic:
/usr/bin/gcc-4.2
can't build much of anything anymore, and it's getting worse by the day.
Abandon 2004!
K
On 2018-11-13, at 7:17 PM, Uli Wienands wrote:
> Ok, now I am really getting confused.
> I cleaned zstd and installed
$ port -v installed zstd
The following ports are currently installed:
zstd @1.3.4_0 (active) platform='darwin 10' archs='x86_64'
date='2018-09-03T16:17:32-0700'
zstd builds on 10.6.8 with a newer compiler. I used clang-3.9.
Nobody on a newer system could know this, so they rely on us "archeolo
Ok, so I did upgrade tk. That went ok, sort of. In the process of
upgrading tk it butchered several other ports ("found 61 broken files, 5
broken ports"). In the process of fixing those it ran aground trying to
install zstd. As a result, my octave 4.2.1 is now kaput :-(.
(Which explains why I
Yes, I am very interested in the Quartz variant. Chris suggested I need to
upgrade my tk so I’ll do that soonest, probably tonight. I’ll check into GTK if
I stil have problems after that.
BTW, I am using your Intel version of Tenfourfox as well. I does run nicely by
and large, although I have h
Hi Uli!
Uli Wienands wrote:
Hi, after Riccardo Mottola mentioned that he contributed a patch to
gimp to make Gimp 2.10 run under 10.6 I tried to install it.
cool :) I suppos eyou atre trying the Quartz variant.
I don't know about your install problem, but it is not direclty gimp
related.
Y
> On 13 Nov 2018, at 3:49 am, Uli Wienands wrote:
>
> Given Ryan's comment I updated my Macports installation (was 2.4.2, now:
> 2.5.4),
Thats a huge jump... if you also had not updated your ports for that period as
well, no surprise you are having problems now. Its really not a good idea t
Given Ryan's comment I updated my Macports installation (was 2.4.2, now:
2.5.4), cleaned gimp2 and tried again... same error. I do this on a
10.6.8 machine, incidentally.
So is there anything else I should/could do?
Log file attached.
Thanks,
Uli
On 11/12/18 12:52 PM, Ryan Schmidt wrote:
On Nov 12, 2018, at 12:47, Uli Wienands wrote:
> Hi, after Riccardo Mottola mentioned that he contributed a patch to gimp to
> make Gimp 2.10 run under 10.6 I tried to install it.
>
> The install went a fair amount but then died at xorg-xorgproto, whatever that
> is, with the error:
>
> Err
Hi, after Riccardo Mottola mentioned that he contributed a patch to gimp
to make Gimp 2.10 run under 10.6 I tried to install it.
The install went a fair amount but then died at xorg-xorgproto, whatever
that is, with the error:
Error: Failed to activate xorg-xorgproto: Image error:
/opt/local
27 matches
Mail list logo
