tech-kern archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: build.sh errors. Maybe serious BUG.



On 22.05.2014 14:51, Ilia Zykov wrote:
> I have a fresh installed system from autobuild.
> NetBSD 6.99.40 (GENERIC) #0: Tue May  6 04:20:54 UTC 2014  
> builds%b2.netbsd.org@localhost:/home/builds/ab/HEAD/amd64/201405060250Z-obj/home/builds/ab/HEAD/src/sys/arch/amd64/compile/GENERIC
>  amd64
> I am going to try this on i386.
> 
> after:
> ===> build.sh command:    ./build.sh -m amd64 -U -j4 -N0 -T 
> /common/orig/amd64/B140522125912/tools -O 
> /common/orig/amd64/B140522125912/obj release

> In file included from 
> /common/orig/src/external/bsd/nvi/dist/regex/regex.h:46:0,
>                  from 
> /common/orig/src/external/bsd/nvi/dist/common/../common/common.h:31,
>                  from /common/orig/src/external/bsd/nvi/dist/common/api.c:36:
> ./common_extern.h:85:26: error: unknown type name 'CL_PRIVATE'
>  int cl_omesg __P((SCR *, CL_PRIVATE *, int));

I found how I can build system, but it is a very strange case.
The main problem was mount point "/common" after I changed it for "/mycom". I 
can build the system.

===> Successful make release
===> build.sh ended:      Thu May 22 23:15:13 MSK 2014
===> Summary of results:
         build.sh command:    ./build.sh -m amd64 -U -j4 -N0 -T 
/mycom/orig/amd64/B140522213413/tools -O /mycom/orig/amd64/B140522213413/obj 
release

$mount
/dev/wd0a on /mycom type ffs (local)
/dev/wd0g on / type ffs (local)
/dev/wd0h on /amd64root type ffs (local)
kernfs on /kern type kernfs (local)
ptyfs on /dev/pts type ptyfs (local)
procfs on /proc type procfs (local)
tmpfs on /var/shm type tmpfs (local)

Ilia.



Home | Main Index | Thread Index | Old Index