Mike Christie wrote: > Jeronimo de A. Barros wrote: >> Hello, >> >> Any help or hint to compile open-iscsi-2.0-870.2 for kernel 2.6.28 ? >> >> I'm trying on a Bluewhite64 12.2 running kernel 2.6.28.2: >> >> r...@test:/usr/local/src/open-iscsi-2.0-870.2# uname -a >> Linux test 2.6.28.2 #1 SMP Sun Feb 1 09:32:16 BRST 2009 x86_64 Intel(R) >> Pentium(R) 4 CPU 3.00GHz GenuineIntel GNU/Linux >> >> r...@test:/usr/local/src/open-iscsi-2.0-870.2# gcc -v >> Reading specs from /usr/lib/gcc/x86_64-pc-linux/4.2.4/specs >> Target: x86_64-pc-linux >> Configured with: ../gcc-4.2.4/configure --prefix=/usr --enable-shared >> --enable-languages=ada,c,c++,fortran,java,objc --disable-multilib >> --enable-threads=posix --enable-__cxa_atexit --disable-checking >> --with-gnu-ld --verbose --build=x86_64-pc-linux --target=x86_64-pc-linux >> --host=x86_64-pc-linux >> Thread model: posix >> gcc version 4.2.4 >> >> I have inserted the line "linux_2_6_28: $(unpatch_code)" but still getting >> errors: >> > > Yeah, that is not going to work, because the 2.6.28 kernel changed some > kernel APIs. The kernel modules need to be updated for the new APIs. I > have done this to the code in git: > git clone git://git.kernel.org/pub/scm/linux/kernel/git/mnc/open-iscsi.git > > I am preparing to do a new release when I finish up integrating some > patches from Fedora, converting code to use strlcat and strlcpy, and fix > some bugs in the iface printing code. I was planning on having this done > by 2.6.29 (so the new release will have 2.6.28 and .29 support). I know > this does not help you much. > > But the upstream 2.6.28.2 kernel is up to date with 870.1 (.2 just has > one fix that 2.6.28 does not for memory leak), so you could just use > those kernel modules and then use the userspace tools from > open-iscsi-2.0-870.2 and you would probably be fine. >
Hi mike, if we are already at the subject. Something I wanted for a while. It is expected for out-of-tree Kernel modules to constantly break at the development edge. What happens today is that I can't finish compiling and installing user-mode tools, if Kernel does not compile. I want to submit a patch that will not force Kernel module compilation by default, but only if say we do "make kernel". Since for me 99% of the time I just want to update on the user-mode, and I'm using the Kernel modules that come from the Kernel I'm using. Is that OK? Boaz --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/open-iscsi -~----------~----~----~----~------~----~------~--~---
