Re: question on porting

2020-06-10 Thread Stefan Eßer
Am 10.06.20 um 16:51 schrieb Donald Wilde:> Okay, it didn't work, but discovered INDEX-12 in /usr/ports, so > ' grep gcc INDEX-12 | wc -l ' worked. My mistake, since you posted on the STABLE mail list but replied to a mail that mentioned INDEX-13: It is INDEX-12 for FreeBSD-12.x and INDEX-13 for

Re: question on porting

2020-06-10 Thread Donald Wilde
On 6/10/20, Matthew Seaman wrote: > On 10/06/2020 15:51, Donald Wilde wrote: >> Okay, it didn't work, but discovered INDEX-12 in /usr/ports, so >> ' grep gcc INDEX-12 | wc -l ' worked. >> >> Such an interesting file, INDEX-12. More research needed. Is it not >> INDEX-13 because I did ' make

Re: question on porting

2020-06-10 Thread Matthew Seaman
On 10/06/2020 15:51, Donald Wilde wrote: Okay, it didn't work, but discovered INDEX-12 in /usr/ports, so ' grep gcc INDEX-12 | wc -l ' worked. Such an interesting file, INDEX-12. More research needed. Is it not INDEX-13 because I did ' make index' instead of ' make fetchindex ' ? You should

Re: question on porting

2020-06-10 Thread Donald Wilde
On 6/10/20, Donald Wilde wrote: > On 6/10/20, Stefan Eßer wrote: >> Am 10.06.20 um 15:45 schrieb Donald Wilde: >>> On 6/10/20, Mark Linimon wrote: On Tue, Jun 09, 2020 at 08:09:21PM -0700, Donald Wilde wrote: > [snip] x3850-1# grep gcc INDEX-13 | wc -l 3848 >>>

Re: question on porting

2020-06-10 Thread Donald Wilde
On 6/10/20, Stefan Eßer wrote: > Am 10.06.20 um 15:45 schrieb Donald Wilde: >> On 6/10/20, Mark Linimon wrote: >>> On Tue, Jun 09, 2020 at 08:09:21PM -0700, Donald Wilde wrote: [snip] >>> x3850-1# grep gcc INDEX-13 | wc -l >>> 3848 >>> >> Hmmm... tried running that and mine doesn't seem

Re: question on porting

2020-06-10 Thread Stefan Eßer
Am 10.06.20 um 15:45 schrieb Donald Wilde: > On 6/10/20, Mark Linimon wrote: >> On Tue, Jun 09, 2020 at 08:09:21PM -0700, Donald Wilde wrote: >>> (and FreeBSD's port maintainers) reach the point of diminishing >>> returns by supporting GCC >> > > Hi, Mark! LTNT2! > >> All you have to do is fix

Re: question on porting

2020-06-10 Thread Donald Wilde
On 6/10/20, Donald Wilde wrote: > On 6/10/20, Mark Linimon wrote: >> On Tue, Jun 09, 2020 at 08:09:21PM -0700, Donald Wilde wrote: >>> (and FreeBSD's port maintainers) reach the point of diminishing >>> returns by supporting GCC >> > > Hi, Mark! LTNT2! > >> All you have to do is fix all the

Re: question on porting

2020-06-10 Thread Donald Wilde
On 6/10/20, Mark Linimon wrote: > On Tue, Jun 09, 2020 at 08:09:21PM -0700, Donald Wilde wrote: >> (and FreeBSD's port maintainers) reach the point of diminishing >> returns by supporting GCC > Hi, Mark! LTNT2! > All you have to do is fix all the ports that have been marked as > depending on

Re: question on porting

2020-06-09 Thread Donald Wilde
On 6/9/20, Donald Wilde wrote: > On 6/9/20, Jonathan Chen wrote: >> On Wed, 10 Jun 2020 at 15:09, Donald Wilde wrote: [snip] >> No, it doesn't. >> > It's not processor speed that is the problem now, although if I alter > those parameters what is now 11 hours will become 20. Such is life > with

Re: question on porting

2020-06-09 Thread Donald Wilde
On 6/9/20, Jonathan Chen wrote: > On Wed, 10 Jun 2020 at 15:09, Donald Wilde wrote: > [...] >> On the specific synth crash, If I re-run it, does synth have code that >> reorders failed ports such that it has a better chance of not having >> such swap-space faults/failures happen? > > No, it

Re: question on porting

2020-06-09 Thread Jonathan Chen
On Wed, 10 Jun 2020 at 15:09, Donald Wilde wrote: [...] > On the specific synth crash, If I re-run it, does synth have code that > reorders failed ports such that it has a better chance of not having > such swap-space faults/failures happen? No, it doesn't. However, if you're experiencing