Hi,
I cannot connect to trac but the main site works fine. Is there a problem with
the server?
R.
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Hi Ryan,
Thank you for the the suggestions! I made some changes in r153861. Please feel
free to make further improvements to the Portfile since it is nomaintainer.
Cheers!
Frank
> On Oct 13, 2016, at 8:35 AM, Ryan Schmidt wrote:
>
>
>> On Oct 12, 2016, at 4:23 PM, m...@macports.org wrote:
> On Oct 14, 2016, at 8:55 AM, René J.V. Bertin wrote:
>
> I cannot connect to trac but the main site works fine. Is there a problem
> with the server?
I have not been able to reach it since last night (~12 hours ago).
vq
___
macports-dev mailing lis
On 2016-10-15 01:12 , Lawrence Velázquez wrote:
On Oct 14, 2016, at 8:55 AM, René J.V. Bertin wrote:
I cannot connect to trac but the main site works fine. Is there a problem with
the server?
I have not been able to reach it since last night (~12 hours ago).
It loaded fine for me just now,
> On Oct 14, 2016, at 10:28 AM, Joshua Root wrote:
>
> It loaded fine for me just now, FWIW.
Same, just tried it.
¯\_(ツ)_/¯
vq
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Some advice appreciated ...
long compiles can take hours
i can ssh into the machine and get it started
sudo port -v install gcc48 gcc5 gcc6 gcc7
that, for example, might take several days to finish (if it does finish)
then I control-Z to pause it, and "bg" to throw it into the background
the
On Oct 14, 2016, at 09:12, Lawrence Velázquez wrote:
>> On Oct 14, 2016, at 8:55 AM, René J.V. Bertin wrote:
>>
>> I cannot connect to trac but the main site works fine. Is there a problem
>> with the server?
>
> I have not been able to reach it since last night (~12 hours ago).
That'll be m
> On Oct 14, 2016, at 7:30 AM, Ken Cunningham
> wrote:
>
> Some advice appreciated …
>
Oh, one more similar question while I’m at it.
I notice mdworker seems to go nuts during these long builds, often appearing to
soak up lots of cycles. I assume it’s trying to index all the build files, et
Hi Ken,
I would really use screen instead and disconnect it and reconnect it later.
David
On Fri, Oct 14, 2016 at 4:30 PM, Ken Cunningham <
ken.cunningham.web...@gmail.com> wrote:
> Some advice appreciated ...
>
>
> long compiles can take hours
>
> i can ssh into the machine and get it started
On Fri, Oct 14, 2016 at 10:30 AM, Ken Cunningham <
ken.cunningham.web...@gmail.com> wrote:
> how exactly do I best find that process to "fg" it again? If I just log
> back in and "fg" it, it is not found. but top shows the process is humming
> away in the background, as expected
>
You can't; it's
> On Oct 14, 2016, at 10:30 AM, Ken Cunningham
> wrote:
>
> long compiles can take hours
>
> i can ssh into the machine and get it started
>
> sudo port -v install gcc48 gcc5 gcc6 gcc7
>
> that, for example, might take several days to finish (if it does
> finish)
>
> then I control-Z to paus
On Oct 14, 2016, at 09:50, Ken Cunningham
wrote:
>
>
>> On Oct 14, 2016, at 7:30 AM, Ken Cunningham
>> wrote:
>>
>> Some advice appreciated …
I use screen for this.
> Oh, one more similar question while I’m at it.
>
> I notice mdworker seems to go nuts during these long builds, often ap
> On Oct 14, 2016, at 10:50 AM, Ken Cunningham
> wrote:
>
> I notice mdworker seems to go nuts during these long builds, often appearing
> to soak up lots of cycles. I assume it’s trying to index all the build files,
> etc
>
> is it easy to sleep that function and then re-enable it after the
On 2016-10-15 01:50 , Ken Cunningham wrote:
I notice mdworker seems to go nuts during these long builds, often appearing to
soak up lots of cycles. I assume it’s trying to index all the build files, etc
is it easy to sleep that function and then re-enable it after the compile is
done?
Not s
Thanks, all — good advice.
K
> On Oct 14, 2016, at 8:14 AM, Joshua Root wrote:
>
> On 2016-10-15 01:50 , Ken Cunningham wrote:
>>
>> I notice mdworker seems to go nuts during these long builds, often appearing
>> to soak up lots of cycles. I assume it’s trying to index all the build
>> fil
On Fri, 14 Oct 2016, Ryan Schmidt wrote:
> On Oct 14, 2016, at 09:50, Ken Cunningham
> wrote:
> > Oh, one more similar question while I'm at it.
> >
> > I notice mdworker seems to go nuts during these long builds, often
> > appearing to soak up lots of cycles. I assume it's trying to index
> >
Hi,
- On 15 Oct, 2016, at 01:05, Fred Wright f...@fwright.net wrote:
> By default, this isn't possible via the GUI, due to the macports
> directory's being hidden.
Use cmd+shift+g in the file chooser.
> One can also accomplish this via:
>
> sudo touch /opt/local/var/macports/build/.
> On Oct 14, 2016, at 7:37 PM, Clemens Lang wrote:
> - On 15 Oct, 2016, at 01:05, Fred Wright f...@fwright.net wrote:
> ...
>> One can also accomplish this via:
>>
>> sudo touch /opt/local/var/macports/build/.metadata_never_index
>>
>> Though I don't know if this works across all OS ver
18 matches
Mail list logo
