On Thu, 15 Nov 2018, j...@tigger.ws wrote:
The new bit is a Telstra NBN modem (for Aus’s new high speed broadband.)
If any Aus user has tamed the Telstra NBN modem please tell me what and
how.
I've had no problem with my NBN stuff; the wireless router connects to the
NBN thing, and the Mac t
> On 15 Nov 2018, at 2:29 pm, Ryan Schmidt wrote:
>
>
>
>> On Nov 15, 2018, at 00:11, j...@tigger.ws wrote:
>>
>> Is the wiki wrong?
>> This does not look correct:
>>
>> [twill] /Users/jam [24]% tail -n 2 /opt/local/etc/macports/sources.conf
>> # rsync://rsync.macports.org/macports/release
On 15 Nov 2018, at 0:50, j...@tigger.ws wrote:
I have installed macports many times, so I’m not naive about what to
do. I’ve never seen this. Can anyone point out my way forward:
[twill] /Users/jam [15]% ping rsync.macports.org
PING ftp.rrze.uni-erlangen.de (131.188.12.211): 56 data bytes
64 b
-I/opt/local/share/cmake/Modules should be -I/opt/local/share/cmake-3.12/Modules
Mark Brethen
mark.bret...@gmail.com
> On Nov 14, 2018, at 11:20 PM, Mark Brethen wrote:
>
> sudo port build getdp +mpich +petsc -python27 +python36 fails. Attaching log.
>
>
>
> Mark Brethen
> mark.bret...@gma
> On Nov 15, 2018, at 00:11, j...@tigger.ws wrote:
>
> Is the wiki wrong?
> This does not look correct:
>
> [twill] /Users/jam [24]% tail -n 2 /opt/local/etc/macports/sources.conf
> # rsync://rsync.macports.org/macports/release/tarballs/ports.tar [default]
> https://distfiles.macports.org/port
Is the wiki wrong?
This does not look correct:
[twill] /Users/jam [24]% tail -n 2 /opt/local/etc/macports/sources.conf
# rsync://rsync.macports.org/macports/release/tarballs/ports.tar [default]
https://distfiles.macports.org/ports.tar.gz [default]
[twill] /Users/jam [25]% sudo port -v selfupdate
I have installed macports many times, so I’m not naive about what to do. I’ve
never seen this. Can anyone point out my way forward:
[twill] /Users/jam [15]% ping rsync.macports.org
PING ftp.rrze.uni-erlangen.de (131.188.12.211): 56 data bytes
64 bytes from 131.188.12.211: icmp_seq=0 ttl=41 time=5
On Nov 14, 2018, at 19:33, Mark Brethen wrote:
> BTW, py36-tables also has those reinplace warnings.
>
> ---> Extracting py36-tables
> Warning: reinplace s:utils.h:xxx_utils.h: didn't change anything in
> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_releas
BTW, py36-tables also has those reinplace warnings.
---> Extracting py36-tables
Warning: reinplace s:utils.h:xxx_utils.h: didn't change anything in
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_python_py-tables/py36-tables/work/tables-3.4
On Nov 14, 2018, at 18:53, Mark Brethen wrote:
> I followed the note below after a selfupdate:
>
> NOTE: Default fortran changed to +gcc8; consider switching variants to enable
> pre-built packages for mpich-default by running:
> "sudo port clean mpich-default && sudo port upgrade mpich-defau
I followed the note below after a selfupdate:
NOTE: Default fortran changed to +gcc8; consider switching variants to enable
pre-built packages for mpich-default by running:
"sudo port clean mpich-default && sudo port upgrade mpich-default
+gcc8-gcc” (should be ggc7)
However it resulted in:
Wa
On Nov 14, 2018, at 15:42, Mark Brethen wrote:
> I performed a selfupdate today and noticed the hdf5 port issued these
> warnings:
>
> Warning: reinplace s|ccache || didn't change anything in
> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs
On Nov 14, 2018, at 16:12, Mark Brethen wrote:
> Unable to configure with given options: FCFLAGS and FFLAGS are both set, but
> with different values (FCFLAGS=-pipe -m64, FFLAGS=-pipe). Attaching log file.
Looks like this has already been reported:
https://trac.macports.org/ticket/57424
And
Unable to configure with given options: FCFLAGS and FFLAGS are both set, but
with different values (FCFLAGS=-pipe -m64, FFLAGS=-pipe). Attaching log file.
main.log
Description: Binary data
Mark Brethen
mark.bret...@gmail.com
I performed a selfupdate today and noticed the hdf5 port issued these warnings:
Warning: reinplace s|ccache || didn't change anything in
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_science_hdf5/hdf5/work/hdf5-1.10.4/tools/src/misc/h5cc
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 14 Nov 2018, at 4:26, Chris Jones wrote:
According to EveryMac.com, MacBook6,1 supports 8GB of RAM. No
futzing would be required. Apple only supports RAM configurations
that were available at the time the model was sold. If 4GB modules
were not available in 2009, then they would not claim t
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
According to EveryMac.com, MacBook6,1 supports 8GB of RAM. No futzing
would be required. Apple only supports RAM configurations that were
available at the time the model was sold. If 4GB modules were not
available in 2009, then they would not claim to support a total of 8GB
of RAM. But accor
26 matches
Mail list logo