First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 97692
Alias:
Product:
Component:
Status: RESOLVED
Resolution: CANTFIX
Assigned To: Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Geaaru <geaaru@gmail.com>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 97692 depends on: Show dependency tree
Bug 97692 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2005-07-02 00:23 0000
Hi, I use kernel 2.6.7 and I try to emerge fuse-2.3.0 on my system but there is
a problem on ebuild.
With this version of kernel (2.6.7) fuse.ko module is not installed on
/lib/modules/2.6.7 directory. While, with 2.6.11.10 installation is ok.
I think that the problem is only on ebuild.
From compilation output I can see that module is compiled, in fact for use it
on my system I must copy fuse.ko from WORKDIR on emerging and than it runs.
Compilation output:
...
* Determining the location of the kernel source code
 * Found kernel source directory:
 *     /usr/src/linux
 * Found sources for kernel version:
 *     2.6.7
 * Converting fuse-2.3.0/kernel/Makefile.in to use M= instead of SUBDIRS= ...  
                                    [ ok ] * Preparing fuse module
 * econf: updating fuse-2.3.0/config.guess with
/usr/share/gnuconfig/config.guess
 * econf: updating fuse-2.3.0/config.sub with /usr/share/gnuconfig/config.sub
./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man
--infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc
--localstatedir=/var/lib --build=i686-pc-linux-gnu --with-kernel=
checking for a BSD-compatible install... /bin/install -c
checking kernel source directory... /usr/src/linux-2.6.7
checking kernel source version... 2.6.7
checking if FUSE is configured in the kernel... no
checking if kernel has extended attribute support... yes
checking if this is user mode linux... no
configure: creating ./config.status
config.status: creating Makefile
config.status: creating config.h
make -C /usr/src/linux-2.6.7
M=/var/tmp/portage/fuse-2.3.0/work/fuse-2.3.0/kernel  modules
make[1]: Entering directory `/usr/src/linux-2.6.7'
  CC [M]  /var/tmp/portage/fuse-2.3.0/work/fuse-2.3.0/kernel/dev.o
  CC [M]  /var/tmp/portage/fuse-2.3.0/work/fuse-2.3.0/kernel/file.o
  CC [M]  /var/tmp/portage/fuse-2.3.0/work/fuse-2.3.0/kernel/dir.o
  CC [M]  /var/tmp/portage/fuse-2.3.0/work/fuse-2.3.0/kernel/inode.o
  LD [M]  /var/tmp/portage/fuse-2.3.0/work/fuse-2.3.0/kernel/fuse.o
  Building modules, stage 2.
  MODPOST
  CC      /var/tmp/portage/fuse-2.3.0/work/fuse-2.3.0/kernel/fuse.mod.o
  LD [M]  /var/tmp/portage/fuse-2.3.0/work/fuse-2.3.0/kernel/fuse.ko
make[1]: Leaving directory `/usr/src/linux-2.6.7'
>>> Test phase [not enabled]: sys-fs/fuse-2.3.0

>>> Install fuse-2.3.0 into /var/tmp/portage/fuse-2.3.0/image/
...

<BUT WHEN IT TRIES TO INSTALL MODULE>
...
make[2]: Nothing to be done for `install-exec-am'.
test -z "/usr/lib/pkgconfig" || mkdir -p --
"/var/tmp/portage/fuse-2.3.0/image//usr/lib/pkgconfig"
 /bin/install -c -m 644 'fuse.pc'
'/var/tmp/portage/fuse-2.3.0/image//usr/lib/pkgconfig/fuse.pc'
make[2]: Leaving directory `/var/tmp/portage/fuse-2.3.0/work/fuse-2.3.0'
make[1]: Leaving directory `/var/tmp/portage/fuse-2.3.0/work/fuse-2.3.0'
dodoc: BUGS does not exist
dodoc: README-2.6 does not exist
 * Installing fuse module
install: cannot stat `fuse.': No such file or directory
man:
prepallstrip:
....

I think that problem is on linux-mod_src_install and/or linux-mod_src_compile
functions.

Thanks. Bye

------- Comment #1 From Stefan Schweizer 2005-07-06 08:09:15 0000 -------
The missing $KV_OBJ seems to be an linux-mod.eclass problem. I fixed the BUGS,
README-2.6 problem in cvs.

------- Comment #2 From Geaaru 2005-07-14 01:39:12 0000 -------
Can you explain step for build fuse module, please? I try to emerge fuse after
a
sync but I have the same problem. Where can I get README-2.6 cvs file for read
instructions?
Thank you very much.
Where Can I see linux-mod.eclass?

------- Comment #3 From Stefan Schweizer 2005-07-14 02:33:16 0000 -------
the eclass is in /usr/portage/eclass

oh, and the README-2.6 does obviously not exist: "dodoc: README-2.6 does not 
exist"

------- Comment #4 From John Mylchreest (RETIRED) 2005-07-14 12:24:28 0000 -------
Sorry, but neither myself or Stefan are able to re-create or even diagnose this
problem.

Please can you try this again using a newer kernel sources release?
If you are still able to re-create please reopen and attach your emerge info output.

------- Comment #5 From Geaaru 2005-07-16 08:12:46 0000 -------
I found a solution. As Stefan Schweizer has said there is a missing on
${KV_OBJ}
variable. But not only. Also ${KV_FULL} is missing. So, I inserted 

get_version 
set_kvobj 

functions before 

einfo "Installing ${modulename} module"

on linux-mod_src_install function (linux-mod.eclass). It was only a "scope of
the variables" problem. Perhaps it is a problem of the my environment
configuration. I don't know. However, now emerge works.

Thanks at all for help.

First Last Prev Next    No search results available      Search page      Enter new bug