error: yacc.h: No such file or directory

classic Classic list List threaded Threaded
23 messages Options
12
Reply | Threaded
Open this post in threaded view
|

error: yacc.h: No such file or directory

Michael Tuexen-3
Dear all,

I'm trying to run
sudo make buildworld
in a directory with r349168.

The result is:
cc  -O2 -pipe -I/usr/home/tuexen/head/usr.bin/mkesdb_static -I/usr/home/tuexen/head/usr.bin/mkesdb_static/../mkesdb  -I/usr/home/tuexen/head/usr.bin/mkesdb_static/../../lib/libc/iconv  -g -MD  -MF.depend.lex.o -MTlex.o -std=gnu99     -I/usr/obj/usr/home/tuexen/head/powerpc.powerpc64/tmp/legacy/usr/include -c lex.c -o lex.o
/usr/home/tuexen/head/usr.bin/mkesdb/lex.l:46:18: error: yacc.h: No such file or directory
/usr/home/tuexen/head/usr.bin/mkesdb/lex.l: In function 'yylex':
/usr/home/tuexen/head/usr.bin/mkesdb/lex.l:60: error: 'R_LN' undeclared (first use in this function)
/usr/home/tuexen/head/usr.bin/mkesdb/lex.l:60: error: (Each undeclared identifier is reported only once
/usr/home/tuexen/head/usr.bin/mkesdb/lex.l:60: error: for each function it appears in.)
/usr/home/tuexen/head/usr.bin/mkesdb/lex.l:72: error: 'yylval' undeclared (first use in this function)
/usr/home/tuexen/head/usr.bin/mkesdb/lex.l:73: error: 'L_IMM' undeclared (first use in this function)
/usr/home/tuexen/head/usr.bin/mkesdb/lex.l:76: error: 'R_NAME' undeclared (first use in this function)
/usr/home/tuexen/head/usr.bin/mkesdb/lex.l:77: error: 'R_ENCODING' undeclared (first use in this function)
/usr/home/tuexen/head/usr.bin/mkesdb/lex.l:78: error: 'R_VARIABLE' undeclared (first use in this function)
/usr/home/tuexen/head/usr.bin/mkesdb/lex.l:79: error: 'R_DEFCSID' undeclared (first use in this function)
/usr/home/tuexen/head/usr.bin/mkesdb/lex.l:80: error: 'R_INVALID' undeclared (first use in this function)
/usr/home/tuexen/head/usr.bin/mkesdb/lex.l:88: error: 'L_STRING' undeclared (first use in this function)
*** Error code 1

Stop.
make[3]: stopped in /usr/home/tuexen/head/usr.bin/mkesdb_static
*** Error code 1

Stop.
make[2]: stopped in /usr/home/tuexen/head
*** Error code 1

Stop.
make[1]: stopped in /usr/home/tuexen/head
*** Error code 1

Stop.
make: stopped in /usr/home/tuexen/head

This is on a 64 bit PPC system. Doing sudo rm -rf /usr/obj does not resolve the issue.

Any idea what is going wrong?

Best regards
Michael
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: error: yacc.h: No such file or directory

Kubilay Kocak
On 18/06/2019 5:42 pm, Michael Tuexen wrote:

> Dear all,
>
> I'm trying to run
> sudo make buildworld
> in a directory with r349168.
>
> The result is:
> cc  -O2 -pipe -I/usr/home/tuexen/head/usr.bin/mkesdb_static -I/usr/home/tuexen/head/usr.bin/mkesdb_static/../mkesdb  -I/usr/home/tuexen/head/usr.bin/mkesdb_static/../../lib/libc/iconv  -g -MD  -MF.depend.lex.o -MTlex.o -std=gnu99     -I/usr/obj/usr/home/tuexen/head/powerpc.powerpc64/tmp/legacy/usr/include -c lex.c -o lex.o
> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:46:18: error: yacc.h: No such file or directory
> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l: In function 'yylex':
> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:60: error: 'R_LN' undeclared (first use in this function)
> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:60: error: (Each undeclared identifier is reported only once
> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:60: error: for each function it appears in.)
> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:72: error: 'yylval' undeclared (first use in this function)
> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:73: error: 'L_IMM' undeclared (first use in this function)
> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:76: error: 'R_NAME' undeclared (first use in this function)
> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:77: error: 'R_ENCODING' undeclared (first use in this function)
> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:78: error: 'R_VARIABLE' undeclared (first use in this function)
> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:79: error: 'R_DEFCSID' undeclared (first use in this function)
> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:80: error: 'R_INVALID' undeclared (first use in this function)
> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:88: error: 'L_STRING' undeclared (first use in this function)
> *** Error code 1
>
> Stop.
> make[3]: stopped in /usr/home/tuexen/head/usr.bin/mkesdb_static
> *** Error code 1
>
> Stop.
> make[2]: stopped in /usr/home/tuexen/head
> *** Error code 1
>
> Stop.
> make[1]: stopped in /usr/home/tuexen/head
> *** Error code 1
>
> Stop.
> make: stopped in /usr/home/tuexen/head
>
> This is on a 64 bit PPC system. Doing sudo rm -rf /usr/obj does not resolve the issue.
>
> Any idea what is going wrong?
>
> Best regards
> Michael

Have seen another report on Twitter yesterday. Didn't see a full build
log, but theirs was had apparently without -j, apparently on June 14
sources:

Error:
/usr/src/usr.bin/mkesdb/lex.1:46:10: fatal error: 'yacc.h' file not found

Have not heard back from them whether it continued after trying -j2 but
I did ask them to hit up freebsd-current if it continued to be an issue

_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: error: yacc.h: No such file or directory

Bob Bishop
Hi,

> On 18 Jun 2019, at 11:56, Kubilay Kocak <[hidden email]> wrote:
>
> On 18/06/2019 5:42 pm, Michael Tuexen wrote:
>> Dear all,
>> I'm trying to run
>> sudo make buildworld
>> in a directory with r349168.

FWIW I have a successful build with r349167

>> The result is:
>> cc  -O2 -pipe -I/usr/home/tuexen/head/usr.bin/mkesdb_static -I/usr/home/tuexen/head/usr.bin/mkesdb_static/../mkesdb  -I/usr/home/tuexen/head/usr.bin/mkesdb_static/../../lib/libc/iconv  -g -MD  -MF.depend.lex.o -MTlex.o -std=gnu99     -I/usr/obj/usr/home/tuexen/head/powerpc.powerpc64/tmp/legacy/usr/include -c lex.c -o lex.o
>> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:46:18: error: yacc.h: No such file or directory
>> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l: In function 'yylex':
>> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:60: error: 'R_LN' undeclared (first use in this function)
>> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:60: error: (Each undeclared identifier is reported only once
>> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:60: error: for each function it appears in.)
>> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:72: error: 'yylval' undeclared (first use in this function)
>> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:73: error: 'L_IMM' undeclared (first use in this function)
>> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:76: error: 'R_NAME' undeclared (first use in this function)
>> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:77: error: 'R_ENCODING' undeclared (first use in this function)
>> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:78: error: 'R_VARIABLE' undeclared (first use in this function)
>> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:79: error: 'R_DEFCSID' undeclared (first use in this function)
>> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:80: error: 'R_INVALID' undeclared (first use in this function)
>> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:88: error: 'L_STRING' undeclared (first use in this function)
>> *** Error code 1
>> Stop.
>> make[3]: stopped in /usr/home/tuexen/head/usr.bin/mkesdb_static
>> *** Error code 1
>> Stop.
>> make[2]: stopped in /usr/home/tuexen/head
>> *** Error code 1
>> Stop.
>> make[1]: stopped in /usr/home/tuexen/head
>> *** Error code 1
>> Stop.
>> make: stopped in /usr/home/tuexen/head
>> This is on a 64 bit PPC system. Doing sudo rm -rf /usr/obj does not resolve the issue.
>> Any idea what is going wrong?
>> Best regards
>> Michael
>
> Have seen another report on Twitter yesterday. Didn't see a full build log, but theirs was had apparently without -j, apparently on June 14 sources:
>
> Error:
> /usr/src/usr.bin/mkesdb/lex.1:46:10: fatal error: 'yacc.h' file not found
>
> Have not heard back from them whether it continued after trying -j2 but I did ask them to hit up freebsd-current if it continued to be an issue


--
Bob Bishop
[hidden email]




_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: error: yacc.h: No such file or directory

Michael Tuexen-3
In reply to this post by Kubilay Kocak
> On 18. Jun 2019, at 12:56, Kubilay Kocak <[hidden email]> wrote:
>
> On 18/06/2019 5:42 pm, Michael Tuexen wrote:
>> Dear all,
>> I'm trying to run
>> sudo make buildworld
>> in a directory with r349168.
>> The result is:
>> cc  -O2 -pipe -I/usr/home/tuexen/head/usr.bin/mkesdb_static -I/usr/home/tuexen/head/usr.bin/mkesdb_static/../mkesdb  -I/usr/home/tuexen/head/usr.bin/mkesdb_static/../../lib/libc/iconv  -g -MD  -MF.depend.lex.o -MTlex.o -std=gnu99     -I/usr/obj/usr/home/tuexen/head/powerpc.powerpc64/tmp/legacy/usr/include -c lex.c -o lex.o
>> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:46:18: error: yacc.h: No such file or directory
>> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l: In function 'yylex':
>> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:60: error: 'R_LN' undeclared (first use in this function)
>> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:60: error: (Each undeclared identifier is reported only once
>> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:60: error: for each function it appears in.)
>> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:72: error: 'yylval' undeclared (first use in this function)
>> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:73: error: 'L_IMM' undeclared (first use in this function)
>> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:76: error: 'R_NAME' undeclared (first use in this function)
>> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:77: error: 'R_ENCODING' undeclared (first use in this function)
>> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:78: error: 'R_VARIABLE' undeclared (first use in this function)
>> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:79: error: 'R_DEFCSID' undeclared (first use in this function)
>> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:80: error: 'R_INVALID' undeclared (first use in this function)
>> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:88: error: 'L_STRING' undeclared (first use in this function)
>> *** Error code 1
>> Stop.
>> make[3]: stopped in /usr/home/tuexen/head/usr.bin/mkesdb_static
>> *** Error code 1
>> Stop.
>> make[2]: stopped in /usr/home/tuexen/head
>> *** Error code 1
>> Stop.
>> make[1]: stopped in /usr/home/tuexen/head
>> *** Error code 1
>> Stop.
>> make: stopped in /usr/home/tuexen/head
>> This is on a 64 bit PPC system. Doing sudo rm -rf /usr/obj does not resolve the issue.
>> Any idea what is going wrong?
>> Best regards
>> Michael
>
> Have seen another report on Twitter yesterday. Didn't see a full build log, but theirs was had apparently without -j, apparently on June 14 sources:
>
> Error:
> /usr/src/usr.bin/mkesdb/lex.1:46:10: fatal error: 'yacc.h' file not found
>
> Have not heard back from them whether it continued after trying -j2 but I did ask them to hit up freebsd-current if it continued to be an issue
OK, I started the build again with -j 2 and it seems that the problem does not occur.

Since I have been using make buildworld without -j n in the past on that machine, the
problem seems to be introduced recently. Any idea what is the cause of the problem?

Best regards
Michael
>

_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: error: yacc.h: No such file or directory

Cy Schubert-4
On June 18, 2019 6:24:36 AM PDT, Michael Tuexen <[hidden email]> wrote:

>> On 18. Jun 2019, at 12:56, Kubilay Kocak <[hidden email]> wrote:
>>
>> On 18/06/2019 5:42 pm, Michael Tuexen wrote:
>>> Dear all,
>>> I'm trying to run
>>> sudo make buildworld
>>> in a directory with r349168.
>>> The result is:
>>> cc  -O2 -pipe -I/usr/home/tuexen/head/usr.bin/mkesdb_static
>-I/usr/home/tuexen/head/usr.bin/mkesdb_static/../mkesdb
>-I/usr/home/tuexen/head/usr.bin/mkesdb_static/../../lib/libc/iconv  -g
>-MD  -MF.depend.lex.o -MTlex.o -std=gnu99    
>-I/usr/obj/usr/home/tuexen/head/powerpc.powerpc64/tmp/legacy/usr/include
>-c lex.c -o lex.o
>>> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:46:18: error: yacc.h: No
>such file or directory
>>> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l: In function 'yylex':
>>> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:60: error: 'R_LN'
>undeclared (first use in this function)
>>> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:60: error: (Each
>undeclared identifier is reported only once
>>> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:60: error: for each
>function it appears in.)
>>> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:72: error: 'yylval'
>undeclared (first use in this function)
>>> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:73: error: 'L_IMM'
>undeclared (first use in this function)
>>> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:76: error: 'R_NAME'
>undeclared (first use in this function)
>>> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:77: error: 'R_ENCODING'
>undeclared (first use in this function)
>>> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:78: error: 'R_VARIABLE'
>undeclared (first use in this function)
>>> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:79: error: 'R_DEFCSID'
>undeclared (first use in this function)
>>> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:80: error: 'R_INVALID'
>undeclared (first use in this function)
>>> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:88: error: 'L_STRING'
>undeclared (first use in this function)
>>> *** Error code 1
>>> Stop.
>>> make[3]: stopped in /usr/home/tuexen/head/usr.bin/mkesdb_static
>>> *** Error code 1
>>> Stop.
>>> make[2]: stopped in /usr/home/tuexen/head
>>> *** Error code 1
>>> Stop.
>>> make[1]: stopped in /usr/home/tuexen/head
>>> *** Error code 1
>>> Stop.
>>> make: stopped in /usr/home/tuexen/head
>>> This is on a 64 bit PPC system. Doing sudo rm -rf /usr/obj does not
>resolve the issue.
>>> Any idea what is going wrong?
>>> Best regards
>>> Michael
>>
>> Have seen another report on Twitter yesterday. Didn't see a full
>build log, but theirs was had apparently without -j, apparently on June
>14 sources:
>>
>> Error:
>> /usr/src/usr.bin/mkesdb/lex.1:46:10: fatal error: 'yacc.h' file not
>found
>>
>> Have not heard back from them whether it continued after trying -j2
>but I did ask them to hit up freebsd-current if it continued to be an
>issue
>OK, I started the build again with -j 2 and it seems that the problem
>does not occur.
>
>Since I have been using make buildworld without -j n in the past on
>that machine, the
>problem seems to be introduced recently. Any idea what is the cause of
>the problem?
>
>Best regards
>Michael
>>
>
>_______________________________________________
>[hidden email] mailing list
>https://lists.freebsd.org/mailman/listinfo/freebsd-current
>To unsubscribe, send any mail to
>"[hidden email]"

This is a generated file. It would appear the make target to build yacc.h hadn't run yet by the time the target that consumed the file ran.

I had a similar problem on Sunday. It wasn't yacc.h but some other file, I cannot remember which. It occurred during one of four buildworlds. Simply restarting the failed buildworld was enough to resolve it.

My hypothesis is a buildworld race. I wonder if some of the recent (over the last week or two) makefile changes exacerbated this issue.


--
Pardon the typos and autocorrect, small keyboard in use.
Cheers,
Cy Schubert <[hidden email]>
FreeBSD UNIX: <[hidden email]> Web: http://www.FreeBSD.org

        The need of the many outweighs the greed of the few.
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: error: yacc.h: No such file or directory

Ian Lepore-3
On Tue, 2019-06-18 at 06:45 -0700, Cy Schubert wrote:

> On June 18, 2019 6:24:36 AM PDT, Michael Tuexen <[hidden email]>
> wrote:
> > > On 18. Jun 2019, at 12:56, Kubilay Kocak <[hidden email]>
> > > wrote:
> > >
> > > On 18/06/2019 5:42 pm, Michael Tuexen wrote:
> > > > Dear all,
> > > > I'm trying to run
> > > > sudo make buildworld
> > > > in a directory with r349168.
> > > > The result is:
> > > > cc  -O2 -pipe -I/usr/home/tuexen/head/usr.bin/mkesdb_static
> >
> > -I/usr/home/tuexen/head/usr.bin/mkesdb_static/../mkesdb
> > -I/usr/home/tuexen/head/usr.bin/mkesdb_static/../../lib/libc/iconv
> >  -g
> > -MD  -MF.depend.lex.o -MTlex.o -std=gnu99    
> > -I/usr/obj/usr/home/tuexen/head/powerpc.powerpc64/tmp/legacy/usr/in
> > clude
> > -c lex.c -o lex.o
> > > > /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:46:18: error:
> > > > yacc.h: No
> >
> > such file or directory
> > > > /usr/home/tuexen/head/usr.bin/mkesdb/lex.l: In function
> > > > 'yylex':
> > > > /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:60: error: 'R_LN'
> >
> > undeclared (first use in this function)
> > > > /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:60: error: (Each
> >
> > undeclared identifier is reported only once
> > > > /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:60: error: for each
> >
> > function it appears in.)
> > > > /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:72: error: 'yylval'
> >
> > undeclared (first use in this function)
> > > > /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:73: error: 'L_IMM'
> >
> > undeclared (first use in this function)
> > > > /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:76: error: 'R_NAME'
> >
> > undeclared (first use in this function)
> > > > /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:77: error:
> > > > 'R_ENCODING'
> >
> > undeclared (first use in this function)
> > > > /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:78: error:
> > > > 'R_VARIABLE'
> >
> > undeclared (first use in this function)
> > > > /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:79: error:
> > > > 'R_DEFCSID'
> >
> > undeclared (first use in this function)
> > > > /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:80: error:
> > > > 'R_INVALID'
> >
> > undeclared (first use in this function)
> > > > /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:88: error:
> > > > 'L_STRING'
> >
> > undeclared (first use in this function)
> > > > *** Error code 1
> > > > Stop.
> > > > make[3]: stopped in /usr/home/tuexen/head/usr.bin/mkesdb_static
> > > > *** Error code 1
> > > > Stop.
> > > > make[2]: stopped in /usr/home/tuexen/head
> > > > *** Error code 1
> > > > Stop.
> > > > make[1]: stopped in /usr/home/tuexen/head
> > > > *** Error code 1
> > > > Stop.
> > > > make: stopped in /usr/home/tuexen/head
> > > > This is on a 64 bit PPC system. Doing sudo rm -rf /usr/obj does
> > > > not
> >
> > resolve the issue.
> > > > Any idea what is going wrong?
> > > > Best regards
> > > > Michael
> > >
> > > Have seen another report on Twitter yesterday. Didn't see a full
> >
> > build log, but theirs was had apparently without -j, apparently on
> > June
> > 14 sources:
> > >
> > > Error:
> > > /usr/src/usr.bin/mkesdb/lex.1:46:10: fatal error: 'yacc.h' file
> > > not
> >
> > found
> > >
> > > Have not heard back from them whether it continued after trying
> > > -j2
> >
> > but I did ask them to hit up freebsd-current if it continued to be
> > an
> > issue
> > OK, I started the build again with -j 2 and it seems that the
> > problem
> > does not occur.
> >
> > Since I have been using make buildworld without -j n in the past on
> > that machine, the
> > problem seems to be introduced recently. Any idea what is the cause
> > of
> > the problem?
> >
> > Best regards
> > Michael
> > >
> >
> > _______________________________________________
> > [hidden email] mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-current
> > To unsubscribe, send any mail to
> > "[hidden email]"
>
> This is a generated file. It would appear the make target to build
> yacc.h hadn't run yet by the time the target that consumed the file
> ran.
>
> I had a similar problem on Sunday. It wasn't yacc.h but some other
> file, I cannot remember which. It occurred during one of four
> buildworlds. Simply restarting the failed buildworld was enough to
> resolve it.
>
> My hypothesis is a buildworld race. I wonder if some of the recent
> (over the last week or two) makefile changes exacerbated this issue.
>
>

Last Saturday, Bryan (cc'd) made a series of commits (r349061-69) that
were all somehow related to dependency processing in the build.  I
don't know the details, just remember seeing some commits about that.

-- Ian

_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: error: yacc.h: No such file or directory

Enji Cooper

> On Jun 18, 2019, at 06:53, Ian Lepore <[hidden email]> wrote:

...

> Last Saturday, Bryan (cc'd) made a series of commits (r349061-69) that
> were all somehow related to dependency processing in the build.  I
> don't know the details, just remember seeing some commits about that.

I remember that as well. This might have changed the dependency order subtly, introducing a race.

The headers might not be built in all cases in time now.

Thanks,
-Enji

PS This is one of the reasons why I wasn’t quick to discount Peter Jeremy’s reported build issue.
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: error: yacc.h: No such file or directory

Enji Cooper

> On Jun 18, 2019, at 06:59, Enji Cooper <[hidden email]> wrote:
>
>
>> On Jun 18, 2019, at 06:53, Ian Lepore <[hidden email]> wrote:
>
> ...
>
>> Last Saturday, Bryan (cc'd) made a series of commits (r349061-69) that
>> were all somehow related to dependency processing in the build.  I
>> don't know the details, just remember seeing some commits about that.
>
> I remember that as well. This might have changed the dependency order subtly, introducing a race.
>
> The headers might not be built in all cases in time now.
>
> Thanks,
> -Enji
>
> PS This is one of the reasons why I wasn’t quick to discount Peter Jeremy’s reported build issue.

Correction: I meant Julian Stacey.
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: error: yacc.h: No such file or directory

Cy Schubert-4
In reply to this post by Michael Tuexen-3
In message <[hidden email]>, Enji
Cooper writes
:

>
>
> > On Jun 18, 2019, at 06:53, Ian Lepore <[hidden email]> wrote:
>
> ...
>
> > Last Saturday, Bryan (cc'd) made a series of commits (r349061-69) that
> > were all somehow related to dependency processing in the build.  I
> > don't know the details, just remember seeing some commits about that.
>
> I remember that as well. This might have changed the dependency order subtly,
>  introducing a race.
--
Cheers,
Cy Schubert <[hidden email]>
FreeBSD UNIX:  <[hidden email]>   Web:  http://www.FreeBSD.org

        The need of the many outweighs the greed of the few.

>
> The headers might not be built in all cases in time now.
>
> Thanks,
> -Enji
>
> PS This is one of the reasons why I wasn’t quick to discount Peter Jeremyâ€
> ™s reported build issue.


_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: error: yacc.h: No such file or directory

Ian Lepore-3
In reply to this post by Enji Cooper
On Tue, 2019-06-18 at 07:01 -0700, Enji Cooper wrote:

> > On Jun 18, 2019, at 06:59, Enji Cooper <[hidden email]>
> > wrote:
> >
> >
> > > On Jun 18, 2019, at 06:53, Ian Lepore <[hidden email]> wrote:
> >
> > ...
> >
> > > Last Saturday, Bryan (cc'd) made a series of commits (r349061-69)
> > > that
> > > were all somehow related to dependency processing in the
> > > build.  I
> > > don't know the details, just remember seeing some commits about
> > > that.
> >
> > I remember that as well. This might have changed the dependency
> > order subtly, introducing a race.
> >
> > The headers might not be built in all cases in time now.
> >
> > Thanks,
> > -Enji
> >
> > PS This is one of the reasons why I wasn’t quick to discount Peter
> > Jeremy’s reported build issue.
>
> Correction: I meant Julian Stacey.

Julian Stacey has 3 problems:

 1. Missing opt_cam.h
 2. Missing yacc.h
 3. A years-long inability to report a problem without hurling personal
insults at the project and everyone associated with it.

Because of #3, I don't much care about 1 and 2.

-- Ian


_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: error: yacc.h: No such file or directory

Cy Schubert-4
In reply to this post by Michael Tuexen-3
In message <[hidden email]>, Enji
Cooper writes
:

>
>
> > On Jun 18, 2019, at 06:59, Enji Cooper <[hidden email]> wrote:
> >
> >
> >> On Jun 18, 2019, at 06:53, Ian Lepore <[hidden email]> wrote:
> >
> > ...
> >
> >> Last Saturday, Bryan (cc'd) made a series of commits (r349061-69) that
> >> were all somehow related to dependency processing in the build.  I
> >> don't know the details, just remember seeing some commits about that.
> >
> > I remember that as well. This might have changed the dependency order subtl
> y, introducing a race.
> >
> > The headers might not be built in all cases in time now.
> >
> > Thanks,
> > -Enji
> >
> > PS This is one of the reasons why I wasn’t quick to discount Peter Jeremy
> ’s reported build issue.

This is why I raised the issue of build race in that thread. My
experience was a different file but it smelled similar. What led me to
believe it was a race was that one of four buildworlds failed for no
logical reason. The other three built fine. And, the failed buildworld
built fine after simply restarting it.

I've experienced these oddities before Bryan's series of commits though
I thought it was a strange coincidence one of four would fail a day
after the makefile changes. Hence my choice of words: exacerbated.

>
> Correction: I meant Julian Stacey.

My issue with Julian was his attack. You can't help people who are on
the warpath.


--
Cheers,
Cy Schubert <[hidden email]>
FreeBSD UNIX:  <[hidden email]>   Web:  http://www.FreeBSD.org

        The need of the many outweighs the greed of the few.




_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: error: yacc.h: No such file or directory

Cy Schubert-4
In reply to this post by Michael Tuexen-3
In message <[hidden email]>
, Ian Le
pore writes:

> On Tue, 2019-06-18 at 07:01 -0700, Enji Cooper wrote:
> > > On Jun 18, 2019, at 06:59, Enji Cooper <[hidden email]>
> > > wrote:
> > >
> > >
> > > > On Jun 18, 2019, at 06:53, Ian Lepore <[hidden email]> wrote:
> > >
> > > ...
> > >
> > > > Last Saturday, Bryan (cc'd) made a series of commits (r349061-69)
> > > > that
> > > > were all somehow related to dependency processing in the
> > > > build.  I
> > > > don't know the details, just remember seeing some commits about
> > > > that.
> > >
> > > I remember that as well. This might have changed the dependency
> > > order subtly, introducing a race.
> > >
> > > The headers might not be built in all cases in time now.
> > >
> > > Thanks,
> > > -Enji
> > >
> > > PS This is one of the reasons why I wasn’t quick to discount Peter
> > > Jeremy’s reported build issue.
> >
> > Correction: I meant Julian Stacey.
>
> Julian Stacey has 3 problems:
>
>  1. Missing opt_cam.h
>  2. Missing yacc.h
>  3. A years-long inability to report a problem without hurling personal
> insults at the project and everyone associated with it.
>
> Because of #3, I don't much care about 1 and 2.

Bingo! My point exactly!


--
Cheers,
Cy Schubert <[hidden email]>
FreeBSD UNIX:  <[hidden email]>   Web:  http://www.FreeBSD.org

        The need of the many outweighs the greed of the few.


_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: error: yacc.h: No such file or directory

Bryan Drewery-6
In reply to this post by Ian Lepore-3
Yes this is likely due to my changes as I removed headers from one of
the forced dependency lists. I'll look at it in a bit.
(I ran several clean and incremental builds without fault but yeah it
could be a race.)
Note my breakage likely only affected world and not kernel so any
opt_*.h isn't new.

Bryan

On 6/18/2019 6:53 AM, Ian Lepore wrote:

> On Tue, 2019-06-18 at 06:45 -0700, Cy Schubert wrote:
>> On June 18, 2019 6:24:36 AM PDT, Michael Tuexen <[hidden email]>
>> wrote:
>>>> On 18. Jun 2019, at 12:56, Kubilay Kocak <[hidden email]>
>>>> wrote:
>>>>
>>>> On 18/06/2019 5:42 pm, Michael Tuexen wrote:
>>>>> Dear all,
>>>>> I'm trying to run
>>>>> sudo make buildworld
>>>>> in a directory with r349168.
>>>>> The result is:
>>>>> cc  -O2 -pipe -I/usr/home/tuexen/head/usr.bin/mkesdb_static
>>>
>>> -I/usr/home/tuexen/head/usr.bin/mkesdb_static/../mkesdb
>>> -I/usr/home/tuexen/head/usr.bin/mkesdb_static/../../lib/libc/iconv
>>>  -g
>>> -MD  -MF.depend.lex.o -MTlex.o -std=gnu99    
>>> -I/usr/obj/usr/home/tuexen/head/powerpc.powerpc64/tmp/legacy/usr/in
>>> clude
>>> -c lex.c -o lex.o
>>>>> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:46:18: error:
>>>>> yacc.h: No
>>>
>>> such file or directory
>>>>> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l: In function
>>>>> 'yylex':
>>>>> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:60: error: 'R_LN'
>>>
>>> undeclared (first use in this function)
>>>>> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:60: error: (Each
>>>
>>> undeclared identifier is reported only once
>>>>> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:60: error: for each
>>>
>>> function it appears in.)
>>>>> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:72: error: 'yylval'
>>>
>>> undeclared (first use in this function)
>>>>> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:73: error: 'L_IMM'
>>>
>>> undeclared (first use in this function)
>>>>> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:76: error: 'R_NAME'
>>>
>>> undeclared (first use in this function)
>>>>> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:77: error:
>>>>> 'R_ENCODING'
>>>
>>> undeclared (first use in this function)
>>>>> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:78: error:
>>>>> 'R_VARIABLE'
>>>
>>> undeclared (first use in this function)
>>>>> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:79: error:
>>>>> 'R_DEFCSID'
>>>
>>> undeclared (first use in this function)
>>>>> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:80: error:
>>>>> 'R_INVALID'
>>>
>>> undeclared (first use in this function)
>>>>> /usr/home/tuexen/head/usr.bin/mkesdb/lex.l:88: error:
>>>>> 'L_STRING'
>>>
>>> undeclared (first use in this function)
>>>>> *** Error code 1
>>>>> Stop.
>>>>> make[3]: stopped in /usr/home/tuexen/head/usr.bin/mkesdb_static
>>>>> *** Error code 1
>>>>> Stop.
>>>>> make[2]: stopped in /usr/home/tuexen/head
>>>>> *** Error code 1
>>>>> Stop.
>>>>> make[1]: stopped in /usr/home/tuexen/head
>>>>> *** Error code 1
>>>>> Stop.
>>>>> make: stopped in /usr/home/tuexen/head
>>>>> This is on a 64 bit PPC system. Doing sudo rm -rf /usr/obj does
>>>>> not
>>>
>>> resolve the issue.
>>>>> Any idea what is going wrong?
>>>>> Best regards
>>>>> Michael
>>>>
>>>> Have seen another report on Twitter yesterday. Didn't see a full
>>>
>>> build log, but theirs was had apparently without -j, apparently on
>>> June
>>> 14 sources:
>>>>
>>>> Error:
>>>> /usr/src/usr.bin/mkesdb/lex.1:46:10: fatal error: 'yacc.h' file
>>>> not
>>>
>>> found
>>>>
>>>> Have not heard back from them whether it continued after trying
>>>> -j2
>>>
>>> but I did ask them to hit up freebsd-current if it continued to be
>>> an
>>> issue
>>> OK, I started the build again with -j 2 and it seems that the
>>> problem
>>> does not occur.
>>>
>>> Since I have been using make buildworld without -j n in the past on
>>> that machine, the
>>> problem seems to be introduced recently. Any idea what is the cause
>>> of
>>> the problem?
>>>
>>> Best regards
>>> Michael
>>>>
>>>
>>> _______________________________________________
>>> [hidden email] mailing list
>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current
>>> To unsubscribe, send any mail to
>>> "[hidden email]"
>>
>> This is a generated file. It would appear the make target to build
>> yacc.h hadn't run yet by the time the target that consumed the file
>> ran.
>>
>> I had a similar problem on Sunday. It wasn't yacc.h but some other
>> file, I cannot remember which. It occurred during one of four
>> buildworlds. Simply restarting the failed buildworld was enough to
>> resolve it.
>>
>> My hypothesis is a buildworld race. I wonder if some of the recent
>> (over the last week or two) makefile changes exacerbated this issue.
>>
>>
>
> Last Saturday, Bryan (cc'd) made a series of commits (r349061-69) that
> were all somehow related to dependency processing in the build.  I
> don't know the details, just remember seeing some commits about that.
>
> -- Ian
>

--
Regards,
Bryan Drewery


signature.asc (631 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: error: yacc.h: No such file or directory

Bryan Drewery-6
In reply to this post by Kubilay Kocak
On 6/18/2019 3:56 AM, Kubilay Kocak wrote:
> Have seen another report on Twitter yesterday. Didn't see a full build
> log, but theirs was had apparently without -j, apparently on June 14
> sources:
>
> Error:
> /usr/src/usr.bin/mkesdb/lex.1:46:10: fatal error: 'yacc.h' file not found
>
> Have not heard back from them whether it continued after trying -j2 but
> I did ask them to hit up freebsd-current if it continued to be an issue

Even -j1 should avoid it. For some reason I am only seeing it without
any -j flag at all.

I should have a fix in soon.

--
Regards,
Bryan Drewery


signature.asc (631 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: error: yacc.h: No such file or directory

Ian Lepore-3
On Tue, 2019-06-18 at 09:51 -0700, Bryan Drewery wrote:

> On 6/18/2019 3:56 AM, Kubilay Kocak wrote:
> > Have seen another report on Twitter yesterday. Didn't see a full
> > build
> > log, but theirs was had apparently without -j, apparently on June
> > 14
> > sources:
> >
> > Error:
> > /usr/src/usr.bin/mkesdb/lex.1:46:10: fatal error: 'yacc.h' file not
> > found
> >
> > Have not heard back from them whether it continued after trying -j2
> > but
> > I did ask them to hit up freebsd-current if it continued to be an
> > issue
>
> Even -j1 should avoid it. For some reason I am only seeing it without
> any -j flag at all.
>
> I should have a fix in soon.
>

There's a subtle difference between -j1 and no -j at all, having to do
with running in "compatibility mode".  I forget the details, but I
remember being burned by the difference once. :)

-- Ian

_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: error: yacc.h: No such file or directory [patch/workaround]

Bryan Drewery-6
On 6/18/2019 10:02 AM, Ian Lepore wrote:

> On Tue, 2019-06-18 at 09:51 -0700, Bryan Drewery wrote:
>> On 6/18/2019 3:56 AM, Kubilay Kocak wrote:
>>> Have seen another report on Twitter yesterday. Didn't see a full
>>> build
>>> log, but theirs was had apparently without -j, apparently on June
>>> 14
>>> sources:
>>>
>>> Error:
>>> /usr/src/usr.bin/mkesdb/lex.1:46:10: fatal error: 'yacc.h' file not
>>> found
>>>
>>> Have not heard back from them whether it continued after trying -j2
>>> but
>>> I did ask them to hit up freebsd-current if it continued to be an
>>> issue
>>
>> Even -j1 should avoid it. For some reason I am only seeing it without
>> any -j flag at all.
>>
>> I should have a fix in soon.
This patch fixes it and allows bin/sh to still build right. I need to
test further before committing though.

http://people.freebsd.org/~bdrewery/patches/dep-headers.diff

That or -j1 is a simple workaround.

>>
>
> There's a subtle difference between -j1 and no -j at all, having to do
> with running in "compatibility mode".  I forget the details, but I
> remember being burned by the difference once. :)
>
> -- Ian
>

Yeah fundamentally this makes sense. There's no dependency defined to
get yacc.h built before lex.o. So the oddness is actually that -j/job
mode gets the order right by accident and that it has a different order
than -B. Shrug.

In bsd.prog.mk historically was this:

.if defined(PROG) && !exists(${.OBJDIR}/${DEPENDFILE})
${OBJS}: ${SRCS:M*.h}
.endif

I changed this mechanism to use OBJS_DEPEND_GUESS which allows a list of
dependencies to apply by checking for the existence of the .depend.foo
file in 1 place. I ended up removing the addition of the headers in
r349061 though while targeting bin/sh build-tools cyclic dependency problem.



--
Regards,
Bryan Drewery


signature.asc (631 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: error: yacc.h: No such file or directory [patch/workaround]

Bryan Drewery-6
On 6/18/2019 10:44 AM, Bryan Drewery wrote:

> On 6/18/2019 10:02 AM, Ian Lepore wrote:
>> On Tue, 2019-06-18 at 09:51 -0700, Bryan Drewery wrote:
>>> On 6/18/2019 3:56 AM, Kubilay Kocak wrote:
>>>> Have seen another report on Twitter yesterday. Didn't see a full
>>>> build
>>>> log, but theirs was had apparently without -j, apparently on June
>>>> 14
>>>> sources:
>>>>
>>>> Error:
>>>> /usr/src/usr.bin/mkesdb/lex.1:46:10: fatal error: 'yacc.h' file not
>>>> found

Fix committed in r349179 (different than my earlier patch). Sorry about
that.

--
Regards,
Bryan Drewery


signature.asc (631 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: error: yacc.h: No such file or directory

Rodney W. Grimes-6
In reply to this post by Cy Schubert-4
> In message <[hidden email]>
> , Ian Le
> pore writes:
> > On Tue, 2019-06-18 at 07:01 -0700, Enji Cooper wrote:
> > > > On Jun 18, 2019, at 06:59, Enji Cooper <[hidden email]>
> > > > wrote:
> > > >
> > > >
> > > > > On Jun 18, 2019, at 06:53, Ian Lepore <[hidden email]> wrote:
> > > >
> > > > ...
> > > >
> > > > > Last Saturday, Bryan (cc'd) made a series of commits (r349061-69)
> > > > > that
> > > > > were all somehow related to dependency processing in the
> > > > > build.  I
> > > > > don't know the details, just remember seeing some commits about
> > > > > that.
> > > >
> > > > I remember that as well. This might have changed the dependency
> > > > order subtly, introducing a race.
> > > >
> > > > The headers might not be built in all cases in time now.
> > > >
> > > > Thanks,
> > > > -Enji
> > > >
> > > > PS This is one of the reasons why I wasn???t quick to discount Peter
> > > > Jeremy???s reported build issue.
> > >
> > > Correction: I meant Julian Stacey.
> >
> > Julian Stacey has 3 problems:
> >
> >  1. Missing opt_cam.h
> >  2. Missing yacc.h
> >  3. A years-long inability to report a problem without hurling personal
> > insults at the project and everyone associated with it.
> >
> > Because of #3, I don't much care about 1 and 2.
>
> Bingo! My point exactly!

You can't understand the frustration of 25 years of
having system build breakage on a pretty regular basis
as a trigger point for anger?

--
Rod Grimes                                                 [hidden email]
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: error: yacc.h: No such file or directory

Warner Losh
On Wed, Jun 19, 2019 at 9:31 AM Rodney W. Grimes <
[hidden email]> wrote:

> > In message <[hidden email]>
> > , Ian Le
> > pore writes:
> > > On Tue, 2019-06-18 at 07:01 -0700, Enji Cooper wrote:
> > > > > On Jun 18, 2019, at 06:59, Enji Cooper <[hidden email]>
> > > > > wrote:
> > > > >
> > > > >
> > > > > > On Jun 18, 2019, at 06:53, Ian Lepore <[hidden email]> wrote:
> > > > >
> > > > > ...
> > > > >
> > > > > > Last Saturday, Bryan (cc'd) made a series of commits
> (r349061-69)
> > > > > > that
> > > > > > were all somehow related to dependency processing in the
> > > > > > build.  I
> > > > > > don't know the details, just remember seeing some commits about
> > > > > > that.
> > > > >
> > > > > I remember that as well. This might have changed the dependency
> > > > > order subtly, introducing a race.
> > > > >
> > > > > The headers might not be built in all cases in time now.
> > > > >
> > > > > Thanks,
> > > > > -Enji
> > > > >
> > > > > PS This is one of the reasons why I wasn???t quick to discount
> Peter
> > > > > Jeremy???s reported build issue.
> > > >
> > > > Correction: I meant Julian Stacey.
> > >
> > > Julian Stacey has 3 problems:
> > >
> > >  1. Missing opt_cam.h
> > >  2. Missing yacc.h
> > >  3. A years-long inability to report a problem without hurling personal
> > > insults at the project and everyone associated with it.
> > >
> > > Because of #3, I don't much care about 1 and 2.
> >
> > Bingo! My point exactly!
>
> You can't understand the frustration of 25 years of
> having system build breakage on a pretty regular basis
> as a trigger point for anger?
>

If there really were 25 years of constant build breakages, then maybe. But
this overstates the number of times it happens. In the past 10 years the
number of tree breakages is 10x or more fewer than in the early days of the
project when it was all the time. In the interim, we've grown a bunch of
new ways to build, and the combinatorics make it impossible to exhaustively
test. No matter what we do, things will break, despite people's best
efforts. Getting table flipping mad is an over-reaction and frankly not
actionable. If you look at the breakage lately, in general it's been in
weird edge cases that not too many people do on a regular basis.

Missing opt_cam.h was only for the not-with-the-kernel build path. It's
supposed to work, but it breaks more often than other paths because it's
significantly less used. This specific issue was actually fixed before
Julian complained as well, so we caught it fairly quickly (I fixed it 5
days after it went in). We should take this as a signal that this feature
isn't used much used, not as an opportunity to vent one's spleen. It's not
even in the CI path today. Had it been, we'd have caught it faster. We hit
this from time to time, so having it be in CI likely makes some sense.

The yacc.h was an unforeseen side effect of improvements in other
dependency parsing that sped up the build. And it was only for the non -j X
/ -B case. Since clang takes forever to build, nobody builds w/o -j #, so
it went unnoticed for a few days. Since it takes a fairly beefy machine to
build FreeBSD, this is an understandable oops. This one I'm not sure we
should put into CI very often since it's a tricky bug to catch and it's
quite rare that we have ordering issues that get tripped up by -j vs no -j.
There's only so many CI resources, and given the problems in the area, I
think it's a poor ROI.

Warner
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: error: yacc.h: No such file or directory

Ian Lepore-3
In reply to this post by Rodney W. Grimes-6
On Wed, 2019-06-19 at 09:30 -0700, Rodney W. Grimes wrote:

> > In message <
> > [hidden email]>
> > , Ian Le
> > pore writes:
> > > On Tue, 2019-06-18 at 07:01 -0700, Enji Cooper wrote:
> > > > > On Jun 18, 2019, at 06:59, Enji Cooper <[hidden email]
> > > > > >
> > > > > wrote:
> > > > >
> > > > >
> > > > > > On Jun 18, 2019, at 06:53, Ian Lepore <[hidden email]>
> > > > > > wrote:
> > > > >
> > > > > ...
> > > > >
> > > > > > Last Saturday, Bryan (cc'd) made a series of commits
> > > > > > (r349061-69)
> > > > > > that
> > > > > > were all somehow related to dependency processing in the
> > > > > > build.  I
> > > > > > don't know the details, just remember seeing some commits
> > > > > > about
> > > > > > that.
> > > > >
> > > > > I remember that as well. This might have changed the
> > > > > dependency
> > > > > order subtly, introducing a race.
> > > > >
> > > > > The headers might not be built in all cases in time now.
> > > > >
> > > > > Thanks,
> > > > > -Enji
> > > > >
> > > > > PS This is one of the reasons why I wasn???t quick to
> > > > > discount Peter
> > > > > Jeremy???s reported build issue.
> > > >
> > > > Correction: I meant Julian Stacey.
> > >
> > > Julian Stacey has 3 problems:
> > >
> > >  1. Missing opt_cam.h
> > >  2. Missing yacc.h
> > >  3. A years-long inability to report a problem without hurling
> > > personal
> > > insults at the project and everyone associated with it.
> > >
> > > Because of #3, I don't much care about 1 and 2.
> >
> > Bingo! My point exactly!
>
> You can't understand the frustration of 25 years of
> having system build breakage on a pretty regular basis
> as a trigger point for anger?
>

I understand how inappropriate it is for a project member to condone or
excuse the verbal abuse of other project members.

Somone with anger management problems likely shouldn't be running
current, where a certain amount of short-term breakage is normal and
expected.

-- Ian

_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
12