Hi,
the latest cctools fails to build on Snow Leopard as follows.
Question: is the compiler critical or can I just configure it with a macports
compiler? which one?
Second question: can it be done automatically?
Riccardo
/usr/bin/gcc-4.2 -Os -std=gnu99 -Os -DLTO_SUPPORT -g -I../../include
AFK right now but I should be able to do something with that. Thanks.
On Friday, August 31, 2018, Chris Jones wrote:
>
> The other thing you could try is run
>
> port outdated
>
> before and after running sync, and compare the results ...
>
> On 31/08/18 12:02, Chris Jones wrote:
>
>>
>>
The other thing you could try is run
port outdated
before and after running sync, and compare the results ...
On 31/08/18 12:02, Chris Jones wrote:
Depends. I work with a full git clone of the ports tree so I see that
being updated and the subsequent portindex running on it.
On 31/08/18
Depends. I work with a full git clone of the ports tree so I see that
being updated and the subsequent portindex running on it.
On 31/08/18 10:30, Bruce Johnson wrote:
Thanks, Chris. What should I see in the output if ports were updated vs.
if no changes occurred?
On Friday, August 31,
Thanks, Chris. What should I see in the output if ports were updated vs. if
no changes occurred?
On Friday, August 31, 2018, Chris Jones wrote:
>
> > sudo port -d sync
>
> On 31/08/18 10:22, Bruce Johnson wrote:
>
>> Hi,
>>
>> Is there any way to determine whether a run of port sync or port
>>
> sudo port -d sync
On 31/08/18 10:22, Bruce Johnson wrote:
Hi,
Is there any way to determine whether a run of port sync or port
selfupdate actually updated any ports? Though it would be nice, I don't
necessarily need to know which ports were updated, just whether or not
*any* ports were
Hi,
Is there any way to determine whether a run of port sync or port selfupdate
actually updated any ports? Though it would be nice, I don't necessarily
need to know which ports were updated, just whether or not *any* ports were
updated.
Thanks.
