On Sat, 14 Nov 2020, Joshua Root wrote:
The MacPorts Project is pleased to announce the release of version
2.6.4. This is a bugfix release with small changes only. See the
ChangeLog [1] for the list of changes.
Which reminds me: OK on latest (and last) Sierra, on an early MacBook Pro
(13", m
> > Perhaps I can upgrade it, but that would be a soldering project.
>
> Aha! That explains it. I was not aware that such machines existed. I
> thought the first Intel Minis had 2 slots that could take 1GB DIMMs.
>
> --
> Bill Cole
Bill, you may be correct! My last bit of internet sleuthing agr
On 29 Nov 2020, at 16:11, Ken Cunningham wrote:
I have a MacMini 1,1 with 1GB of Ram that runs either MacOS X 10.4 or
10.5. It doesn’t have enough ram to run 10.6. Perhaps I can upgrade
it, but that would be a soldering project. I use it to build
TenFourFox for Intel which I upload to the TenF
> $ xsltproc dyld: Library not loaded: /opt/local/lib/libicui18n.65.dylib
> Referenced from: /opt/local/bin/xsltproc Reason: image not found Trace/BPT
> trap
This shows that icu was upgraded to version 67, but that port is still linked
against 65.
Usually a rev-bump would have taken care of t
Hi,
I was about to fail a bug, ascii doc doesn't build for me, nor does
vala.
I get this issue, e.g.
:info:build a2x: ERROR: "xsltproc" --stringparam callout.graphics 0
--stringparam navig.graphics 0 --stringparam admon.textlabel 1
--stringparam admon.graphics 0
"/opt/local/var/macports/
> Can you explain any practical justification for supporting Leopard on
> Intel?
>
> I'm not suggesting that it's in any way "wrong" but I just can't see
> where the utility for such machines is. I'm still making use of a 2006
> Core Duo iMac which is 10.6/i386, so I'm familiar with the fact t
On 29 Nov 2020, at 6:55, Riccardo Mottola via macports-users wrote:
This is all on 10.5/i386 - then I already started my luck on PPC, then
10.6/universal - and last 10.5/x86_64
Can you explain any practical justification for supporting Leopard on
Intel?
I'm not suggesting that it's in any w
On 29 Nov 2020, at 6:02, Gerben Wierda via macports-users wrote:
I think I shared this before, but I’m not certain so I am doing so
now (again).
The MacPorts postfix master process will not launch reliably at boot
if it is set up with ‘port load postfix’. The reason for the
unreliable boot i
I have a patch for gcc that forces it to use the old assembler ever if
clang-5.0 is installed. I haven't pushed it yet, but I can send it to you if
you like.
The binaries server I put up basically _is_ an Intel builder...covers 10.4 &
10.5 PPC and Intel. Use it if you want.
Glad you're well! B
On Nov 29, 2020, at 06:24, Riccardo Mottola wrote:
> On 2020-11-17 00:30:33 + Ryan Schmidt wrote:
>
>> On Nov 16, 2020, at 17:58, Riccardo Mottola wrote:
>
>>> Here were are in the situation that if, for some upstream reason, libxml2
>>> stops compiling with gcc 4.2, the user has no work
Hi,
On 2020-11-14 22:29:52 + Ken Cunningham
wrote:
>
>
>> On Nov 14, 2020, at 1:39 PM, Jeffrey Walton wrote:
>
>> You can disable Clang's integrated assembler with -no-integrated-as,
>> if needed. I've had to use it several times because Clang cannot
>> consume the same programs as GCC
Hi Ken!
On 2020-11-14 20:56:20 + Ken Cunningham
wrote:
> One last thing…
>
> this noise:
>
> :485:11: warning: section "__textcoal_nt" is deprecated
> .section __TEXT,__textcoal_nt,coalesced,pure_instructions
> ^ ~
> :485:11: note: change secti
Hi,
On 2020-11-17 00:30:33 + Ryan Schmidt
wrote:
On Nov 16, 2020, at 17:58, Riccardo Mottola wrote:
Here were are in the situation that if, for some upstream reason,
libxml2
stops compiling with gcc 4.2, the user has no workaround and is
stuck in an
endless dependency.
If such
Hi,
On 2020-11-14 20:38:43 + Ryan Schmidt wrote:
> On Nov 14, 2020, at 14:31, Ken Cunningham wrote:
>
>> I’m not positive, but I think at one point in time macports base added
>> this flag to most or all builds, but that went by the wayside when most
>> builds became 64bit intel.
>
> I
Hi Ken,
On 2020-11-18 17:07:43 + Ken Cunningham
wrote:
Riccardo et al,
I have finished rebuilding all the common compilers for Leopard Intel
i386,
up to clang-9.0.
It is apparently possible now to build up to gcc-10 on Tiger and up,
and I
have built some of these, but MacPorts ha
Hi,
after some days with the "head under water" I had time to resume work on
MacPorts upgrades.
I restarted and the error I pasted below happened for me e.g. in gcc 48 and
gcc6 upgrade.
On 2020-11-14 20:31:40 + Ken Cunningham
wrote:
>> ld: illegal text-relocation to '___cpu_indicator_i
I think I shared this before, but I’m not certain so I am doing so now (again).
The MacPorts postfix master process will not launch reliably at boot if it is
set up with ‘port load postfix’. The reason for the unreliable boot is that
macOS during boot for about 60 seconds or so claims port 25 (a
17 matches
Mail list logo
