Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 06 Aug 2007 11:59:55 -0500
From:      Kevin Kramer <kramer@centtech.com>
To:        pluknet <pluknet@gmail.com>
Cc:        freebsd-stable@freebsd.org
Subject:   Re: buildkernel failure
Message-ID:  <46B7538B.7080307@centtech.com>
In-Reply-To: <a31046fc0708040503w5f87602al3d6b63ba07fc31d0@mail.gmail.com>
References:  <46B0A7D5.6040308@centtech.com>	 <a31046fc0708011522h682fd9cfk88fd5ffc98b65719@mail.gmail.com>	 <46B398B6.4040705@centtech.com> <a31046fc0708040503w5f87602al3d6b63ba07fc31d0@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
thanks. I cvs'd this morning and manually did the patch and finally got 
built and running 6.2S now on to my real problem.. next post.

------------------------------

Kevin Kramer
Sr. Systems Administrator
512.418.5725
Centaur Technology, Inc.
www.centtech.com



pluknet wrote the following on 08/04/07 07:03:
> On 04/08/07, Kevin Kramer <kramer@centtech.com> wrote:
>   
>>  ok, thanks. I have made that change and now I've gotten this
>>
>>  /usr/src/sys/ufs/ffs/ffs_vfsops.c: In function
>> `ffs_mountfs':
>> /usr/src/sys/ufs/ffs/ffs_vfsops.c:675: error: structure has
>> no member named `mnt_gjprovider'
>> /usr/src/sys/ufs/ffs/ffs_vfsops.c:677: error: structure has
>> no member named `mnt_gjprovider'
>> /usr/src/sys/ufs/ffs/ffs_vfsops.c:678: error: structure has
>> no member named `mnt_gjprovider'
>> /usr/src/sys/ufs/ffs/ffs_vfsops.c:678: error: structure has
>> no member named `mnt_gjprovider'
>> /usr/src/sys/ufs/ffs/ffs_vfsops.c:687: error: structure has
>> no member named `mnt_gjprovider'
>> /usr/src/sys/ufs/ffs/ffs_vfsops.c:688: error: structure has
>> no member named `mnt_gjprovider'
>> /usr/src/sys/ufs/ffs/ffs_vfsops.c:696: error: structure has
>> no member named `mnt_gjprovider'
>> /usr/src/sys/ufs/ffs/ffs_vfsops.c:865: error: structure has
>> no member named `mnt_gjprovider'
>> /usr/src/sys/ufs/ffs/ffs_vfsops.c:866: error: structure has
>> no member named `mnt_gjprovider'
>> /usr/src/sys/ufs/ffs/ffs_vfsops.c:867: error: structure has
>> no member named `mnt_gjprovider'
>> /usr/src/sys/ufs/ffs/ffs_vfsops.c: In function
>> `ffs_unmount':
>> /usr/src/sys/ufs/ffs/ffs_vfsops.c:1028: error: structure
>> has no member named `mnt_gjprovider'
>> /usr/src/sys/ufs/ffs/ffs_vfsops.c:1029: error: structure
>> has no member named `mnt_gjprovider'
>> /usr/src/sys/ufs/ffs/ffs_vfsops.c:1030: error: structure
>> has no member named `mnt_gjprovider'
>> *** Error code 1
>>
>> I've searched the threads and found nothing so far relevant.
>>
>>     
>
> Things are changed also a bit in src/sys/sys/mount.h
> with v1.197.2.7 since that patch was prepared,
> so it fails to apply against releng_6 cleanly.
>
> You can apply this manually to fix the build:
> @@ -178,6 +178,7 @@
>         int             mnt_secondary_accwrites;/* (i) secondary wr. starts */
>         int             mnt_ref;                /* (i) Reference count */
>         int             mnt_gen;                /* struct mount generation */
> +       char            *mnt_gjprovider;        /* gjournal provider name */
>  };
>
>  struct vnode *__mnt_vnode_next(struct vnode **mvp, struct mount *mp);
>
>
> wbr,
> pluknet
>   



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46B7538B.7080307>