Re: Build error on current@r296308: 'yacc.h' file not found

On Wed, Mar 2, 2016 at 11:04 AM, Bryan Drewery wrote: > On 3/2/2016 12:52 PM, Bryan Drewery wrote: >> On 3/2/2016 11:00 AM, Kurt Jaeger wrote: >>> Hi! >>> >>> Today, I upgraded to r296308 and had this failure during buildworld: >>> >>> ===> usr.bin/mkesdb_static

Re: Build error on current@r296308: 'yacc.h' file not found

On 3/2/2016 12:52 PM, Bryan Drewery wrote: > On 3/2/2016 11:00 AM, Kurt Jaeger wrote: >> Hi! >> >> Today, I upgraded to r296308 and had this failure during buildworld: >> >> ===> usr.bin/mkesdb_static (obj,build-tools) >> cc -O2 -pipe -I/usr/src/usr.bin/mkesdb_static >>

Re: Build error on current@r296308: 'yacc.h' file not found

Hi! > I have the same compilation error when I tried to build current today as well. /usr/src/usr.bin/mkcsmapper/Makefile.inc has the same problem. -- p...@opsec.eu+49 171 3101372 4 years to go ! ___

Re: Build error on current@r296308: 'yacc.h' file not found

On 3/2/2016 11:00 AM, Kurt Jaeger wrote: > Hi! > > Today, I upgraded to r296308 and had this failure during buildworld: > > ===> usr.bin/mkesdb_static (obj,build-tools) > cc -O2 -pipe -I/usr/src/usr.bin/mkesdb_static > -I/usr/src/usr.bin/mkesdb_static/../mkesdb >

Re: Build error on current@r296308: 'yacc.h' file not found

I have the same compilation error when I tried to build current today as well. On Wed, Mar 2, 2016 at 11:48 AM, Kurt Jaeger wrote: > Hi! > >> Today, I upgraded to r296308 and had this failure during buildworld: >> >> ===> usr.bin/mkesdb_static (obj,build-tools) >> cc -O2 -pipe

Re: Build error on current@r296308: 'yacc.h' file not found

Hi! > Today, I upgraded to r296308 and had this failure during buildworld: > > ===> usr.bin/mkesdb_static (obj,build-tools) > cc -O2 -pipe -I/usr/src/usr.bin/mkesdb_static > -I/usr/src/usr.bin/mkesdb_static/../mkesdb > -I/usr/src/usr.bin/mkesdb_static/../../lib/libc/iconv -g -std=gnu99 >

Build error on current@r296308: 'yacc.h' file not found

Hi! Today, I upgraded to r296308 and had this failure during buildworld: ===> usr.bin/mkesdb_static (obj,build-tools) cc -O2 -pipe -I/usr/src/usr.bin/mkesdb_static -I/usr/src/usr.bin/mkesdb_static/../mkesdb -I/usr/src/usr.bin/mkesdb_static/../../lib/libc/iconv -g -std=gnu99

Build error on CURRENT

I'm getting a compile error during buildworld here: === libexec/atrun (all) cc -g -DATJOB_DIR=\/var/at/jobs/\ -DLFILE=\/var/at/jobs/.lockfile\ -DLOADAVG_MX=1.5 -DATSPOOL_DIR=\/var/at/spool\ -DVERSION=\2.9\ -DDAEMON_UID=1 -DDAEMON_GID=1 -DDEFAULT_BATCH_QUEUE=\'E\' -DDEFAULT_AT_QUEUE=\'c\'

Re: Xorg build error on -current-amd64

Hello. I've just had this error yesterday. It seems, that utmp.h file is still in the system. Make in /usr/src: make delete-old and try again . David Rhodus wrote: ===Verifying install for sessreg in /usr/ports/x11/sessreg === Building for sessreg-1.0.5 make all-am cc -std=gnu99 -Wall

Re: Xorg build error on -current-amd64

Thanks, make delete-old fixed everything. On Thu, Jun 3, 2010 at 4:43 AM, Alexander Pyhalov a...@rsu.ru wrote: Hello. I've just had this error yesterday. It seems, that utmp.h file is still in the system. Make in /usr/src: make delete-old and try again . David Rhodus wrote: ===    

Xorg build error on -current-amd64

===Verifying install for sessreg in /usr/ports/x11/sessreg === Building for sessreg-1.0.5 make all-am cc -std=gnu99 -Wall -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -fno-strict-aliasing -Wbad-function-cast -Wformat=2

Re: wierd build error with -current

On 30 Jun 2001 21:59:19 -0700, Matthew Jacob wrote: I'm sure you're right. I guess I need to go fix the breakage. It's supposed to work. Things get built in /usr/obj, not /usr/src. Hrm, OK. That's something I didn't know. I'm assuming that you've tried mounting /usr/src as read-write and

Re: wierd build error with -current

On 29 Jun 2001 14:46:38 -0700, Matthew Jacob wrote: I now mount my /usr/src read-only. That should work? Ask yourself the question: I've mounted a filesystem read-only. Should I be able to write to that filesystem?. I'm now getting: [ .. ] Permission denied This is strange. Is this an

Re: wierd build error with -current

No, the build process is broken. It is in fact supposed to work, and worked last week, to build from a read-only /usr/src. On 30 Jun 2001, Andrew Reid wrote: On 29 Jun 2001 14:46:38 -0700, Matthew Jacob wrote: I now mount my /usr/src read-only. That should work? Ask yourself the

Re: wierd build error with -current

On 30 Jun 2001 09:39:15 -0700, Matthew Jacob wrote: No, the build process is broken. It is in fact supposed to work, and worked last week, to build from a read-only /usr/src. How do you qualify this? The error you got was Permission denied. The build process will want to write files. Your

Re: wierd build error with -current

Andrew Reid wrote: On 30 Jun 2001 09:39:15 -0700, Matthew Jacob wrote: No, the build process is broken. It is in fact supposed to work, and worked last week, to build from a read-only /usr/src. How do you qualify this? The error you got was Permission denied. The build process will want

Re: wierd build error with -current

I'm sure you're right. I guess I need to go fix the breakage. It's supposed to work. Things get built in /usr/obj, not /usr/src. On 1 Jul 2001, Andrew Reid wrote: On 30 Jun 2001 09:39:15 -0700, Matthew Jacob wrote: No, the build process is broken. It is in fact supposed to work, and

wierd build error with -current

I now mount my /usr/src read-only. That should work? I'm now getting: cc -nostdinc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc_r/../libc/i nclude -DPTHREAD_KERNEL -D_THREAD_SAFE -I/usr/src/lib/libc_r/uthread -I/usr/src/ lib/libc_r/../../include -D_LOCK_DEBUG -D_PTHREADS_INVARIANTS