Date: Wed, 10 Jun 2020 06:45:12 -0700 From: Donald Wilde <dwilde1@gmail.com> To: freebsd-stable <freebsd-stable@freebsd.org> Subject: Re: question on porting Message-ID: <CAEC7391nBLW2VuUiSCsM80PDS3Y8HFJexOu0Vx-1SaucqrhWuw@mail.gmail.com> In-Reply-To: <20200610102415.GC4411@lonesome.com> References: <CAEC73934akXpUU50Z8WDS0nakQ5Dy73FhTGUh8vpKv%2B8r0ArEg@mail.gmail.com> <20200610102415.GC4411@lonesome.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 6/10/20, Mark Linimon <linimon@lonesome.com> 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? *
****************************************************
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAEC7391nBLW2VuUiSCsM80PDS3Y8HFJexOu0Vx-1SaucqrhWuw>