DragonFly BSD
DragonFly bugs List (threaded) for 2005-08
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: HEADS UP: Custom config and HEAD


From: Chris Pressey <cpressey@xxxxxxxxxxxxxxx>
Date: Wed, 3 Aug 2005 13:13:18 -0700

On Wed, 3 Aug 2005 19:26:51 +0000
David Rhodus <sdrhodus@xxxxxxxxx> wrote:

> On 8/3/05, Chris Pressey <cpressey@xxxxxxxxxxxxxxx> wrote:
> > On Tue, 2 Aug 2005 03:35:42 +0200
> > Joerg Sonnenberger <joerg@xxxxxxxxxxxxxxxxx> wrote:
> > 
> > > On Mon, Aug 01, 2005 at 06:11:59PM -0700, Matthew Dillon wrote:
> > > >
> > > > :
> > > > :Hi all,
> > > > :I want to warn you that I'll soon commit the stat(2) changes
> > > > and if you :have a custom kernel config, you really want to have
> > > > COMPAT_DF12, :otherwise the kernel won't even make it through a
> > > > reboot. :
> > > > :Joerg
> > > >
> > > >     Hmm.  This makes me a bit uncomfortable.  I'm worried that
> > > >     we are going to get a ton of bug reports from people who get
> > > >     caught out in the code, despite the warning.  Maybe we
> > > >     should invert the sense of  the option.  e.g.
> > > >     NO_COMPAT_DF12.
> > >
> > > I've been thinking about making it non-optional for while, but
> > > that wouldn't fix the problem. I also don't like negative options,
> > > since they tend to obscure code. This instance is different from
> > > COMPAT_43, since I intend to keep it really optional, e.g. if you
> > > have a clean world, you don't need it.
> > 
> > FWIW I can't seem to get cvsup binary, built since this change, to
> > work. The package builds fine, but trying to use it produces gems
> > like:
> > 
> > 
> > %cvsup ~/cvsup/bsdinstaller-repo-supfile
> > Nonexistent base directory "/home/installer" for collection
> > "installer" %ll /home/installer/
> > total 6
> > drwxr-xr-x  3 catseye  wheel  1024 Aug  2 12:05 CVSROOT
> > drwxr-xr-x  7 catseye  wheel   512 Aug  3 11:50 installer
> > drwxr-xr-x  3 catseye  wheel   512 Mar 20 19:32 sup
> > 
> > 
> > I thought this might be because I didn't rebuild ezm3.  So I tried
> > rebuilding ezm3 and I got this:
> > 
> > 
> > ...
> > boot-FreeBSD4/m3build/FreeBSD4/m3build -T ../m3config/src
> > -DBOOTSTRAP=TRUE -DBUILD_ALL -DSHIP_ALL
> > 
> > 
> > ***
> > *** runtime error:
> > ***    gc: Could not extend the traced heap
> > ***
> > 
> >   use option @M3stackdump to get a stack trace
> > mkdir FreeBSD4
> > --- building in FreeBSD4 ---
> > gmake: *** [packages] Abort trap (core dumped)
> > *** Error code 2
> > 
> > Stop in /usr/ports/lang/ezm3.
> > 
> > 
> > Any ideas?
> > 
> > -Chris
> > 
> 
> cvsup seems to build fine under pkgsrc.

I don't think it's a packaging system problem; I can't get either ezm3
version 1.1 or version 1.2 to build from source.  I suspect it's a
problem with ezm3's "FreeBSD 4 bootstrap kit" - possibly it makes undue
assumptions about the stat structures.

I see no reason to suspect that PM3's or CM3's FreeBSD 4 bootstrap would
work any better.

What's even more worrisome is that 'fetch' just gave me the following error:

%fetch ftp://ftp.freebsd.org/pub/FreeBSD/development/CVSup/ezm3/ezm3-1.1-src.tar.bz2
fetch: ftp://ftp.freebsd.org/pub/FreeBSD/development/CVSup/ezm3/ezm3-1.1-src.tar.bz2:
Syntax error, command unrecognized

The same command works fine on a FreeBSD 4.9 box.

-Chris



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