> On May 31, 2017, at 18:24, Richard L. Hamilton wrote:
>
> The default compiler didn't like the option -std=c++11. When I ran with
> configure.compiler=macports-clang-3.8 (which was perhaps the newest of what I
> had installed), it coped with that, but later got errors as shown in the
> att
The default compiler didn't like the option -std=c++11. When I ran with
configure.compiler=macports-clang-3.8 (which was perhaps the newest of what I
had installed), it coped with that, but later got errors as shown in the
attached log file.
main.log-poppler.txt.gz
Description: GNU Zip compr
On May 31, 2017, at 11:12 AM, db wrote:
> On 31 May 2017, at 15:16, Daniel J. Luke wrote:
>> yes, but base doesn't currently know that it should do that (this thread
>> contains some suggestions about how that might be possible).
>
> I meant doing this from within base for the handful of utilit
Hi,
You should start by following the instructions macports gave you at the
end of the messages below :-
Error: See
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_autogen/autogen/main.log
for details.
Error: rev-upgrade
Hi,
I am using Mac Sierra 10.12.5. I installed macPorts, gcc46 and other bunch
of stuffs. macPorts seems broken. I got similar errors for all 'port
install' command.
sudo port install gcc46
Password:
---> Computing dependencies for gcc46
---> Cleaning gcc46
---> Scanning binaries for linki
On 31 May 2017, at 15:16, Daniel J. Luke wrote:
> yes, but base doesn't currently know that it should do that (this thread
> contains some suggestions about how that might be possible).
I meant doing this from within base for the handful of utilities they are — no
prio ports, no soft deps.
On May 31, 2017, at 8:36 AM, db wrote:
> When running port upgrade outdated, couldn't base just deactivate those
> utilities, upgrade them first and unattended rebuild broken ports/files,
> which is what the user eventually does manually?
yes, but base doesn't currently know that it should do t
On 30 May 2017, at 17:08, Ryan Schmidt wrote:
> To fix this to your satisfaction, i.e. in a way that the user does not
> encounter an error message that they have to fix manually, we would have to
> modify every port that has such a configure script to tell it to only use the
> system versions
