Hi again, Cyril,

I was able to get the SVN glibc-bsd repository trunk with kfreebsd-6 in it,
and it seems to be building OK. I didn't realize that the source was ported
to build under GNU utilities. So far, so good. I appreciate you guys
pointing me in the right direction.

Ian

On Dec 4, 2007 9:43 AM, Ian Bonnycastle <[EMAIL PROTECTED]> wrote:

> Hi Cyril,
>
> Sorry I'm coming back to this subject again, but the kfreebsd6-source
> package doesn't appear to have a "debian" directory under it, so there is no
> way to use the dpkg-buildpackage scripts with it. I'm going to have to
> resort to compiling the source code of the actual FreeBSD 6.2 kernel, but
> I'm not sure where the BSD-aware tools are (I think they're under
> /usr/lib/freebsd, so I'll give that a try first.)
>
> Is the fact that the kfreebsd-6.2 source package (the package, not the
> FreeBSD 6.2 source code) is missing the debian directory an oversight, or
> on purpose?
>
> Ian
>
> On Nov 20, 2007 7:11 PM, Cyril Brulebois <[EMAIL PROTECTED]
> > wrote:
>
> > On 20/11/2007, Ian Bonnycastle wrote:
> > > Hi everyone,
> >
> > Hello,
> >
> > > I'm a new user to kFreeBSD, and I've been trying to figure out how to
> > > recompile the kernel. I downloaded the kFreeBSD-source package,
> > > compiled (with some difficulty) the config program under
> > > sys/usr.sbin/config, but then am stuck trying to use that config
> > > program. It currently keeps telling me:
> > >
> > > "no ident line specified"
> > >
> > > Am I supposed to be using a custom config with the kFreeBSD config
> > > command? Or is there a more automatic way to recompile the kernel?
> >
> > I'm not sure whether you're talking about a FreeBSD tarball or about the
> > kfreebsd-source-* packages[1].
> >
> >  1. http://packages.debian.org/kfreebsd-source
> >
> > Using tools like "dpkg-buildpackage" or "debuild" should be sufficient
> > once you've fetched the debian source package, unpacked it, and possibly
> >
> > customized it.
> >
> > Good luck.
> >
> > Cheers,
> >
> > --
> > Cyril Brulebois
> >
>
>

Reply via email to