b.t.w. gcc 4.8 is quite old now. If you have any ports installed using
this gcc version, as a variant, you should check to see if the defaults
for that port have been updated to a newer release (gcc 6) and where
necessary switch to using that.
On 06/03/17 08:46, Chris Jones wrote:
Hi,
You haven't really provided any useful information that anyone can use
to help. For instance the last line of the log you posted says
:debug:build "$procedure $targetname"
:error:build See
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc48/gcc48/main.log
for details.
Have you followed that advice and looked at that log ?
Chris
On 05/03/17 17:59, Comer Duncan wrote:
I have had a failure to complete an update using a script that I have
used for quite a while. I attach the script and the end part of the
main.log. Can someone please take a look and offer some likely cause(s)?
Thanks very much.
Comer
