Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 6 Jul 2000 20:45:50 -0500 (CDT)
From:      Mike Silbersack <silby@silby.com>
To:        Doug Barton <DougB@gorean.org>
Cc:        hackers@freebsd.org, stable@freebsd.org
Subject:   Re: [Fwd: Re: Cant build 3.5-stable?]
Message-ID:  <Pine.BSF.4.21.0007062044130.43878-100000@achilles.silby.com>
In-Reply-To: <Pine.BSF.4.21.0007061926180.56862-100000@achilles.silby.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Ok, the problem seems to stem from the fact that if I do a buildworld, I
get the following:


achilles# vi /usr/obj/usr/src/lib/libfetch/fetch_err.h

/* Generated from /usr/src/lib/libfetch/fetch_err.et */

#ifndef __fetch_err_h__
#define __fetch_err_h__

#include <com_right.h>

void initialize_ftch_error_table_r(struct et_list **);

void initialize_ftch_error_table(void);
#define init_ftch_err_tbl initialize_ftch_error_table

typedef enum ftch_error_number{
        ERROR_TABLE_BASE_ftch = -2098765312,
        ftch_err_base = -2098765312,
        FETCH_ABORT = -2098765312,
        FETCH_AUTH = -2098765311,
        FETCH_DOWN = -2098765310,
        FETCH_EXISTS = -2098765309,
        FETCH_FULL = -2098765308,
        FETCH_INFO = -2098765307,
        FETCH_MEMORY = -2098765306,

(etc)

You may note that this differs greatly from what you get if you just go
into /usr/src/lib/libfetch and make clean ; make.

Anyone with a better knowledge of the buildworld process have any ideas?

Mike "Silby" Silbersack

On Thu, 6 Jul 2000, Mike Silbersack wrote:

> The problem seems to stem from a corrupt 
> /usr/obj/usr/src/lib/libfetch/fetch_err.h
> 
> If I manually delete it and make from the libfetch directory, it seems
> to be created properly.
> 
> So, I have two lingering questions:
> 
> 1.  Did the tools used to create the file change?  As far as I can tell,
> libfetch itself did _not_ change from 3.4 to 3.5.
> 
> 2.  Why isn't the file auto-cleaned?
> 
> On the other hand, I haven't run a full buildworld yet, so it could be
> something else in the build process casuing the problem.  Details after it
> finishes.
> 
> Mike "Silby" Silbersack



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0007062044130.43878-100000>