Graphene Build Error

Ryan Schmidt ryandesign at macports.org
Tue Jul 3 21:18:53 UTC 2018


Remember to Reply All so the conversation stays on the list.


On Jul 3, 2018, at 16:08, Curtis Matz wrote:

> On Jul 3, 2018, at 3:12 PM, Ryan Schmidt wrote:
> 
>> Are you sure the logfile doesn't exist? It should, and we would need to see its contents to know for sure what happened. But I see you're building graphene universal, and I expect all users who attempt to do so will currently experience this problem: https://trac.macports.org/ticket/56766
> 
> less /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_graphene/graphene/main.log
> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_graphene/graphene/main.log: No such file or directory

If this was after running your custom ports update script, which cleans all installed ports, that would make sense, if you have a previous version of graphene installed. Cleaning deletes the log file, among other things.


> On Jul 3, 2018, at 3:12 PM, Ryan Schmidt wrote:
> 
>> What was the command you ran? This error message suggests you were asking MacPorts to do something to a port or set of ports that didn't exist.
> 
> I run my custom ports update script.  Here’s the content of that file.
> 
> #!/bin/sh
> if [ "$(whoami)" != 'root' ]; then
>   echo "command line: sudo myports"
>   exit 1
> fi
> 
> port selfupdate
> port outdated
> port upgrade outdated
> port uninstall inactive
> port uninstall leaves
> port clean --all installed >> /dev/null 2>&1

Ok, that makes sense. I guess you didn't have any inactive and/or leaf ports to uninstall, hence the error.



More information about the macports-users mailing list