Re: question on porting
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 -CURRENT (which will become FreeBSD-13.0 at a later time ...) ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: question on porting
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 index' instead of ' make fetchindex ' ? > > You should always get an index matching the major version of the OS > you're using, whether you fetch something pre-built or make you own. > Makes sense! Obviously a lot of you guys are "STABLE-ising" 13 now! >>> Memo to self: figure out what basic options are supported in >>> Makefiles, especially in/usr/ports/, and make clear documentation >>> patches (if needed). :D >>> >> /self thinks this is all probably in the Porter's Handbook, but the >> regular Handbook should have some of it. > > The ports(7) man page probably has a lot of what you're looking for. > Okay! > There's a 'make search' command which is a wrapper around grepping in > the INDEX file that you might find interesting. > > For your use case, try: > > cd /usr/ports > make search bdeps=gcc display=name > > which returns 3241 results when I tried it just now. > Oh, that is interesting too. Figures that FreeBSD Project would have THE most powerful c/c++ make infrastructure out there! i am impressed. This is so much better than Ubuntu, even with Synaptic for its ports. Although I am experimenting with a GUI on the mule, all interaction will eventually be ssh in the intended configuration. Thanks to you all! I think I consider this [SOLVED] for now. Will keep learning! :D -- Don Wilde * What is the Internet of Things but a system * * of systems including humans? * ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: question on porting
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 always get an index matching the major version of the OS you're using, whether you fetch something pre-built or make you own. Memo to self: figure out what basic options are supported in Makefiles, especially in/usr/ports/, and make clear documentation patches (if needed). :D /self thinks this is all probably in the Porter's Handbook, but the regular Handbook should have some of it. The ports(7) man page probably has a lot of what you're looking for. There's a 'make search' command which is a wrapper around grepping in the INDEX file that you might find interesting. For your use case, try: cd /usr/ports make search bdeps=gcc display=name which returns 3241 results when I tried it just now. Cheers, Matthew ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: question on porting
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 >>> Hmmm... tried running that and mine doesn't seem to find INDEX-13 as a >>> file. >>> >>> Tried ' find / -name "INDEX-13" ' >> >> You have to either create or fetch the INDEX file: >> >> $ cd /usr/ports >> $ make index >> >> or >> >> $ cd /usr/ports >> $ make fetchindex >> >> Regards, STefan >> > Thanks, Stefan! > 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 ' ? > Memo to self: figure out what basic options are supported in > Makefiles, especially in /usr/ports/, and make clear documentation > patches (if needed). :D > /self thinks this is all probably in the Porter's Handbook, but the regular Handbook should have some of it. -- Don Wilde * What is the Internet of Things but a system * * of systems including humans? * ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: question on porting
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 to find INDEX-13 as a >> file. >> >> Tried ' find / -name "INDEX-13" ' > > You have to either create or fetch the INDEX file: > > $ cd /usr/ports > $ make index > > or > > $ cd /usr/ports > $ make fetchindex > > Regards, STefan > Thanks, Stefan! Memo to self: figure out what basic options are supported in Makefiles, especially in /usr/ports/, and make clear documentation patches (if needed). :D -- Don Wilde * What is the Internet of Things but a system * * of systems including humans? * ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: question on porting
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 all the ports that have been marked as >> depending on GCC (in most cases, because they fail to build on >> clang): >> >> x3850-1# grep gcc INDEX-13 | wc -l >> 3848 >> > Hmmm... tried running that and mine doesn't seem to find INDEX-13 as a file. > > Tried ' find / -name "INDEX-13" ' You have to either create or fetch the INDEX file: $ cd /usr/ports $ make index or $ cd /usr/ports $ make fetchindex Regards, STefan ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: question on porting
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 ports that have been marked as
>> depending on GCC (in most cases, because they fail to build on
>> clang):
>>
>> x3850-1# grep gcc INDEX-13 | wc -l
>> 3848
>>
> Hmmm... tried running that and mine doesn't seem to find INDEX-13 as a
> file.
>
> Tried ' find / -name "INDEX-13" '
>
> What else might be different? Is this part of your grep, like as in '
> grep the 13th line of every port {xyz} file ' ? Should I do that
> search with '-R' ... no, that didn't work either.
>
> ' grep -R "INDEX-13" * ' from / is not returning results either. Are
> you using a variant of standard grep?
Whoops ... trying ' grep -R gcc "INDEX-13" * ' from /
I am now getting some .ko files that match this string from
/boot/kernel, after a warning that INDEX-13 doesn't exist in root.
Still chewing away...
--
Don Wilde
* What is the Internet of Things but a system *
* of systems including humans? *
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: question on porting
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 GCC (in most cases, because they fail to build on
> clang):
>
> x3850-1# grep gcc INDEX-13 | wc -l
> 3848
>
Hmmm... tried running that and mine doesn't seem to find INDEX-13 as a file.
Tried ' find / -name "INDEX-13" '
What else might be different? Is this part of your grep, like as in '
grep the 13th line of every port {xyz} file ' ? Should I do that
search with '-R' ... no, that didn't work either.
' grep -R "INDEX-13" * ' from / is not returning results either. Are
you using a variant of standard grep?
--
Don Wilde
* What is the Internet of Things but a system *
* of systems including humans? *
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: question on porting
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 "old" computers... :D > -- BTW, both "old" and "speed" are relative. My first computer was an Intel SDK-86 @ 500 Hz, It had 2048 words of 16-bit static RAM and 2x that in EPROM. -- Don Wilde * What is the Internet of Things but a system * * of systems including humans? * ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: question on porting
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 doesn't. > > However, if you're experiencing crashes it may be better for you to > lower your "Number_of_builders" and/or "Max_jobs_per_builder" in your > /usr/local/etc/synth/synth.ini. > Thanks, Jon. I'll look at that after this finishes and after I fix the known OOPS I caused myself. What happened is that it was building both llvm80 and gcc9 at the same time. I can see that now it's building llvm90 and it's been at it for over 2 hours. Obviously this is going to become a problem again although the next time I build a disk I can use more of it for swap. 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 "old" computers... :D -- Don Wilde * What is the Internet of Things but a system * * of systems including humans? * ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: question on porting
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 crashes it may be better for you to lower your "Number_of_builders" and/or "Max_jobs_per_builder" in your /usr/local/etc/synth/synth.ini. Cheers. -- Jonathan Chen ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
