Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 170450 - sys-cluster/gfs-kernel-1.03.00 compile error on 2.6.20-r2
Summary: sys-cluster/gfs-kernel-1.03.00 compile error on 2.6.20-r2
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Gentoo Cluster Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: kernel-2.6.20
  Show dependency tree
 
Reported: 2007-03-11 17:40 UTC by Christian R
Modified: 2010-09-10 18:51 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
gfs-kernel-1.04 EBUILD (gfs-kernel-1.04.00.ebuild,1.42 KB, text/plain)
2007-03-21 18:40 UTC, Jasmine
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Christian R 2007-03-11 17:40:10 UTC
the error:

 * Found sources for kernel version:
 *     2.6.20-gentoo-r2
>>> Unpacking source...
>>> Unpacking cluster-1.03.00.tar.gz to /var/tmp/portage/sys-cluster/gfs-kernel-1.03.00/work
>>> Source unpacked.
>>> Compiling source in /var/tmp/portage/sys-cluster/gfs-kernel-1.03.00/work/cluster-1.03.00/gfs-kernel ...

Configuring Makefiles for your system...
------------------------------------------------
--------------------------------
Completed Makefile configuration

cd src && make all
make[1]: Entering directory `/var/tmp/portage/sys-cluster/gfs-kernel-1.03.00/work/cluster-1.03.00/gfs-kernel/src'
cd harness && make all
make[2]: Entering directory `/var/tmp/portage/sys-cluster/gfs-kernel-1.03.00/work/cluster-1.03.00/gfs-kernel/src/harness'
rm -f linux
ln -s . linux
make -C /usr/src/linux M=/var/tmp/portage/sys-cluster/gfs-kernel-1.03.00/work/cluster-1.03.00/gfs-kernel/src/harness symverfile=/usr/src/linux/../kernel/cluster/dlm.symvers modules USING_KBUILD=yes
make[3]: Entering directory `/usr/src/linux-2.6.20-gentoo-r2'
  CC [M]  /var/tmp/portage/sys-cluster/gfs-kernel-1.03.00/work/cluster-1.03.00/gfs-kernel/src/harness/main.o
/var/tmp/portage/sys-cluster/gfs-kernel-1.03.00/work/cluster-1.03.00/gfs-kernel/src/harness/main.c:121: error: syntax error before "lm_fsdata_t"
/var/tmp/portage/sys-cluster/gfs-kernel-1.03.00/work/cluster-1.03.00/gfs-kernel/src/harness/main.c:123: warning: function declaration isn't a prototype
/var/tmp/portage/sys-cluster/gfs-kernel-1.03.00/work/cluster-1.03.00/gfs-kernel/src/harness/main.c: In function `lm_mount':
/var/tmp/portage/sys-cluster/gfs-kernel-1.03.00/work/cluster-1.03.00/gfs-kernel/src/harness/main.c:135: error: `proto_name' undeclared (first use in this function)
/var/tmp/portage/sys-cluster/gfs-kernel-1.03.00/work/cluster-1.03.00/gfs-kernel/src/harness/main.c:135: error: (Each undeclared identifier is reported only once
/var/tmp/portage/sys-cluster/gfs-kernel-1.03.00/work/cluster-1.03.00/gfs-kernel/src/harness/main.c:135: error: for each function it appears in.)
/var/tmp/portage/sys-cluster/gfs-kernel-1.03.00/work/cluster-1.03.00/gfs-kernel/src/harness/main.c:161: error: `table_name' undeclared (first use in this function)
/var/tmp/portage/sys-cluster/gfs-kernel-1.03.00/work/cluster-1.03.00/gfs-kernel/src/harness/main.c:161: error: `host_data' undeclared (first use in this function)
/var/tmp/portage/sys-cluster/gfs-kernel-1.03.00/work/cluster-1.03.00/gfs-kernel/src/harness/main.c:162: error: `cb' undeclared (first use in this function)
/var/tmp/portage/sys-cluster/gfs-kernel-1.03.00/work/cluster-1.03.00/gfs-kernel/src/harness/main.c:162: error: `fsdata' undeclared (first use in this function)
/var/tmp/portage/sys-cluster/gfs-kernel-1.03.00/work/cluster-1.03.00/gfs-kernel/src/harness/main.c:162: error: `min_lvb_size' undeclared (first use in this function)
/var/tmp/portage/sys-cluster/gfs-kernel-1.03.00/work/cluster-1.03.00/gfs-kernel/src/harness/main.c:162: error: `lockstruct' undeclared (first use in this function)
/var/tmp/portage/sys-cluster/gfs-kernel-1.03.00/work/cluster-1.03.00/gfs-kernel/src/harness/main.c:162: error: too few arguments to function
make[4]: *** [/var/tmp/portage/sys-cluster/gfs-kernel-1.03.00/work/cluster-1.03.00/gfs-kernel/src/harness/main.o] Error 1
make[3]: *** [_module_/var/tmp/portage/sys-cluster/gfs-kernel-1.03.00/work/cluster-1.03.00/gfs-kernel/src/harness] Error 2
make[3]: Leaving directory `/usr/src/linux-2.6.20-gentoo-r2'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/var/tmp/portage/sys-cluster/gfs-kernel-1.03.00/work/cluster-1.03.00/gfs-kernel/src/harness'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/var/tmp/portage/sys-cluster/gfs-kernel-1.03.00/work/cluster-1.03.00/gfs-kernel/src'
make: *** [all] Error 2

!!! ERROR: sys-cluster/gfs-kernel-1.03.00 failed.
Call stack:
  ebuild.sh, line 1614:   Called dyn_compile
  ebuild.sh, line 971:   Called qa_call 'src_compile'
  environment, line 3973:   Called src_compile
  gfs-kernel-1.03.00.ebuild, line 49:   Called die

!!! compile problem
!!! If you need support, post the topmost build error, and the call stack if relevant.
!!! A complete build log is located at '/var/tmp/portage/sys-cluster/gfs-kernel-1.03.00/temp/build.log'.

Reproducible: Always
Comment 1 Jasmine 2007-03-21 18:40:24 UTC
Created attachment 113996 [details]
gfs-kernel-1.04 EBUILD

cluster-1.03 doesn't work with kernel 2.6.20
upgrade all packages in sys-cluster (ccs, cman, cman-headers, cman-kernel, dlm, dlm-headers, dlm-kernel, fence, gfs-headers, gnbd, gnbd-headers, gnbd-kernel, magma, magma-plugins) to version 1.04, and also upgrade sys-fs/gfs to 1.04, then use the ebuild attached to upgrade sys-cluster/gfs-kernel to 1.04 (not yet merged in portage). I don't know why that was the only package left out of portage, but it works for me(tm).
Using 2.6.20-gentoo-r3

Good luck.
Comment 2 Christian R 2007-03-26 08:14:06 UTC
it works, thank you
Comment 3 Markus Schlegel 2007-04-26 08:24:53 UTC
(In reply to comment #1)
> Created an attachment (id=113996) [edit]
> gfs-kernel-1.04 EBUILD
> 
> cluster-1.03 doesn't work with kernel 2.6.20
> upgrade all packages in sys-cluster (ccs, cman, cman-headers, cman-kernel, dlm,
> dlm-headers, dlm-kernel, fence, gfs-headers, gnbd, gnbd-headers, gnbd-kernel,
> magma, magma-plugins) to version 1.04, and also upgrade sys-fs/gfs to 1.04,
> then use the ebuild attached to upgrade sys-cluster/gfs-kernel to 1.04 (not yet
> merged in portage). I don't know why that was the only package left out of
> portage, but it works for me(tm).
> Using 2.6.20-gentoo-r3
> 
> Good luck.
> 

This new version doesn't work with gentoo-sources-2.6.19-r5 (which is amd64-stable today). it compiles fine with gentoo-sources-2.6.20-r6

...
  CC [M]  /var/tmp/portage/sys-cluster/gfs-kernel-1.04.00/work/cluster-1.04.00/gfs-kernel/src/gfs/diaper.o
  CC [M]  /var/tmp/portage/sys-cluster/gfs-kernel-1.04.00/work/cluster-1.04.00/gfs-kernel/src/gfs/dio.o
/var/tmp/portage/sys-cluster/gfs-kernel-1.04.00/work/cluster-1.04.00/gfs-kernel/src/gfs/diaper.c: In Funktion »get_dummy_sb«:
/var/tmp/portage/sys-cluster/gfs-kernel-1.04.00/work/cluster-1.04.00/gfs-kernel/src/gfs/diaper.c:235: Fehler: »struct block_device« hat kein Element namens »bd_mount_sem«
/var/tmp/portage/sys-cluster/gfs-kernel-1.04.00/work/cluster-1.04.00/gfs-kernel/src/gfs/diaper.c:237: Fehler: »struct block_device« hat kein Element namens »bd_mount_sem«
make[4]: *** [/var/tmp/portage/sys-cluster/gfs-kernel-1.04.00/work/cluster-1.04.00/gfs-kernel/src/gfs/diaper.o] Fehler 1
make[4]: *** Warte auf noch nicht beendete Prozesse...
/var/tmp/portage/sys-cluster/gfs-kernel-1.04.00/work/cluster-1.04.00/gfs-kernel/src/gfs/dio.c: In Funktion »stuck_releasepage«:
/var/tmp/portage/sys-cluster/gfs-kernel-1.04.00/work/cluster-1.04.00/gfs-kernel/src/gfs/dio.c:85: Warnung: format »%lu« erwartet Typ »long unsigned int«, aber Argument 3 hat Typ »sector_t«
/var/tmp/portage/sys-cluster/gfs-kernel-1.04.00/work/cluster-1.04.00/gfs-kernel/src/gfs/dio.c:96: Warnung: format »%lu« erwartet Typ »long unsigned int«, aber Argument 4 hat Typ »uint64_t«
/var/tmp/portage/sys-cluster/gfs-kernel-1.04.00/work/cluster-1.04.00/gfs-kernel/src/gfs/dio.c:122: Warnung: format »%lu« erwartet Typ »long unsigned int«, aber Argument 3 hat Typ »uint64_t«
/var/tmp/portage/sys-cluster/gfs-kernel-1.04.00/work/cluster-1.04.00/gfs-kernel/src/gfs/dio.c:122: Warnung: format »%lu« erwartet Typ »long unsigned int«, aber Argument 4 hat Typ »uint64_t«
make[3]: *** [_module_/var/tmp/portage/sys-cluster/gfs-kernel-1.04.00/work/cluster-1.04.00/gfs-kernel/src/gfs] Fehler 2
make[3]: Leaving directory `/usr/src/linux-2.6.19-gentoo-r5'
make[2]: *** [all] Fehler 2
make[2]: Leaving directory `/var/tmp/portage/sys-cluster/gfs-kernel-1.04.00/work/cluster-1.04.00/gfs-kernel/src/gfs'
make[1]: *** [all] Fehler 2
make[1]: Leaving directory `/var/tmp/portage/sys-cluster/gfs-kernel-1.04.00/work/cluster-1.04.00/gfs-kernel/src'
make: *** [all] Fehler 2

!!! ERROR: sys-cluster/gfs-kernel-1.04.00 failed.
Call stack:
  ebuild.sh, line 1614:   Called dyn_compile
  ebuild.sh, line 971:   Called qa_call 'src_compile'
  environment, line 4078:   Called src_compile
  gfs-kernel-1.04.00.ebuild, line 51:   Called die
Comment 4 Jasmine 2007-05-16 07:11:06 UTC
(In reply to comment #3)
> This new version doesn't work with gentoo-sources-2.6.19-r5 (which is
> amd64-stable today). it compiles fine with gentoo-sources-2.6.20-r6

It seems "gfs-kernel-1.04.00" was not released with 2.6.19 in mind.. I tried modifying the instances of "down(&real->bd_mount_sem);" with "mutex_lock(&real->bd_mount_mutex);" and replacing "up(&real->bd_mount_sem);" with  "mutex_unlock(&real->bd_mount_mutex);" in both gfs-kernel/src/gfs/diaper.c and gfs-kernel/src/gfs/ops_fstype.c, which got me past the errors you pasted, but only to encounter heaps of other problems which tells me that gfs-kernel-1.04.00 probably started around the time of kernel-2.6.20

So, if you need gfs-kernel to work with kernel-2.6.19, then stick with gfs-kernel-1.03.00

cheers

Comment 5 Jasmine 2007-05-16 07:16:35 UTC
In case anyone is curious, my comment above in regards to making gfs-kernel-1.04.00 work with kernel-2.6.19 was based on some patch posted on cluster-devel mailing list to make the stable branch work with the 2.6.17 kernel, and not just randomly guessing:
http://www.redhat.com/archives/cluster-devel/2006-June/msg00101.html

Comment 6 Jakub Moc (RETIRED) gentoo-dev 2007-09-11 11:06:39 UTC
1.04 in the tree since May.