Subject: Re: 20021003 build src problem.
To: Dawid Szymanski <dawszy@polnet.wroc.pl>
From: Mihai Chelaru <kefren@netbastards.org>
List: current-users
Date: 10/03/2002 12:24:15
I was about to 'call' about the same problem. The strange thing is that the 
same sources worked on two systems when updating from 1.6G and 1.6BETA4. But 
on the third (updating a dual-pentium from 1.6B-sommerfeld) I got the same 
errors as you did.

M

On Thursday 03 October 2002 12:12, Dawid Szymanski wrote:
> dependall ===> libhdb
> CC=/usr/tools/bin/i386--netbsdelf-gcc /usr/tools/bin/nbmkdep -a  -I.       
>                              -I/usr/src/crypto/dist/heimdal/lib/hdb        
>     -I/usr/obj/lib/libasn1                          -I/usr/obj/lib/libkrb5 
>   -I/usr/src/crypto/dist/heimdal/lib/krb5         
> -I/usr/src/crypto/dist/heimdal/lib/asn1                
> -I/usr/src/crypto/dist/heimdal/lib/com_err                
> -I/usr/src/include/heimdal      -I/usr/src/lib/libroken          
> -I/usr/src/crypto/dist/heimdal/lib/roken                 -DHAVE_CONFIG_H
> -nostdinc -isystem /usr/include 
> /usr/src/crypto/dist/heimdal/lib/hdb/common.c
> /usr/src/crypto/dist/heimdal/lib/hdb/db.c
> /usr/src/crypto/dist/heimdal/lib/hdb/db3.c
> /usr/src/crypto/dist/heimdal/lib/hdb/hdb-ldap.c
> /usr/src/crypto/dist/heimdal/lib/hdb/hdb.c
> /usr/src/crypto/dist/heimdal/lib/hdb/keytab.c
> /usr/src/crypto/dist/heimdal/lib/hdb/mkey.c
> /usr/src/crypto/dist/heimdal/lib/hdb/ndbm.c
> /usr/src/crypto/dist/heimdal/lib/hdb/print.c asn1_Key.c asn1_Event.c
> asn1_HDBFlags.c asn1_hdb_entry.c asn1_Salt.c asn1_GENERATION.c hdb_err.c
> asn1_Key.c:4: libasn1.h: No such file or directory
> asn1_Event.c:4: libasn1.h: No such file or directory
> asn1_HDBFlags.c:4: libasn1.h: No such file or directory
> asn1_hdb_entry.c:4: libasn1.h: No such file or directory
> asn1_Salt.c:4: libasn1.h: No such file or directory
> asn1_GENERATION.c:4: libasn1.h: No such file or directory
> nbmkdep: compile failed.
> *** Error code 1
>
> Stop.
> nbmake: stopped in /usr/src/lib/libhdb
> *** Error code 1
>
>
>
> Any clue?