[Bug 1695736] Re: fails to run: support missing from kernel
Adam, Lack of a blcr-dkms package in Zesty likely means that BLCR does not support kernels as new as used in this distro (unless it has been renamed?). Unfortunately, that means no BLCR. So, I am surprised that the other blcr packages are distributed at all. I am the "upstream" for BLCR, but I cannot answer for how BLCR is being packaged for Zesty. Hopefully the package maintainer (Alan Woodland, IIRC) will respond at some point. -Paul -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1695736 Title: fails to run: support missing from kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blcr/+bug/1695736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1695736] Re: fails to run: support missing from kernel
Adam, Is the blcr-dkms package installed? That is the ubuntu package containing the kernel modules. FWIW: blcr-dkms is not listed as dependency for the blcr package because that would create an unwarranted dependency for multiple MPI packages which are built with BLCR support but most frequently used without BLCR. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1695736 Title: fails to run: support missing from kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blcr/+bug/1695736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1695736] Re: fails to run: support missing from kernel
Adam, This error indicates that the kernel modules for BLCR are not loaded. Unless something has changed recently in the packaging for BLCR, the kernel modules should be loaded automatically at boot. However, if you have not rebooted since the install, they might not be. Is you run "/sbin/lsmod | grep blcr" do you see any output? If not, "modprobe blcr" as root will hopefully resolve the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1695736 Title: fails to run: support missing from kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blcr/+bug/1695736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1515072] Re: clang segfaults on hello world on arm64
I have been successfully using 1:3.6.2-3ubuntu2 on arm64 since some time after it appeared in wily-proposed. I have just now removed and re-installed from the xenial repository to be certain. Clang-3.6 is indeed working now. IMHO, this bug may be closed. -Paul -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1515072 Title: clang segfaults on hello world on arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.6/+bug/1515072/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1515072] [NEW] clang segfaults on hello world on arm64
Public bug reported: The following Debian bug is present in clang-3.6-1:3.6.2-1 (which is the current version for arm64/wily) https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801695 Note that bug report is closed, indicating that the problem is resolved in clang-3.6-1:3.6.2-2 ** Affects: llvm-toolchain-3.6 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1515072 Title: clang segfaults on hello world on arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.6/+bug/1515072/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1357795] Re: gnuradio dose not work 14.04 libboost1.48 requested
There is absolutely no connection between blcr and gnuradio or libboost. This bug should not be reported against package=blcr. ** Package changed: blcr (Ubuntu) = gnuradio (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1357795 Title: gnuradio dose not work 14.04 libboost1.48 requested To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnuradio/+bug/1357795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1289083] Re: blcr-dkms 0.8.5-2.1: blcr kernel module failed to build [configure: error: Kernel source is configured uni-processor but the kernel symbol table is SMP.]
FYI: A beta release of BLCR 0.8.6 is now in Debian Experimental and should resolve this bug. Hopefully once 0.8.6 is out of Beta, the Debian package will move out of Experimental. -Paul -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1289083 Title: blcr-dkms 0.8.5-2.1: blcr kernel module failed to build [configure: error: Kernel source is configured uni-processor but the kernel symbol table is SMP.] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blcr/+bug/1289083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1198804] Re: blcr-dkms 0.8.5-2: blcr kernel module failed to build [error: too few arguments to function ‘do_mmap_pgoff’]
This is a known up-steam issue. BLCR does not yet support 3.8.x and newer kernels. -Paul (the up-stream maintainer) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1198804 Title: blcr-dkms 0.8.5-2: blcr kernel module failed to build [error: too few arguments to function ‘do_mmap_pgoff’] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blcr/+bug/1198804/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 804943] Re: blcr kernel module failed to build with kernel 3.0 : configure: error: --with-linux argument '3.0-x' is neither a kernel version string nor a full path
Joni-Pekka, For those folk that saw this error when upgrading their system, but only had BLCR's kernel modules installed due to a recommends from another package, removal of the blcr-dkms package was (and still is) a viable solution. For those who need a *functional* BLCR, it was initially reasonable to expect them hold back updates of their kernel - but too much time has passed for that to be a good solution anymore. While not fixes in the sense of making BLCR work on the current kernels, these were both well-intentioned and appropriate work-arounds when they were posted. If you had consulted the mailing list for the BLCR project, you would know that support for kernels through 3.7.1 is currently in Beta testing. [See https://hpcrdm.lbl.gov/pipermail/checkpoint/2013-January/000550.html for the latest] If you had followed the link at the top of this bug report to the corresponding Debian bug (#638339), or had consulted packages.debian.org, you would know that the blcr-0.8.5~b2 (beta) is already in Debian Experimental. This is the reason for the Bug Update Watcher item that immediately precedes your first comment. I understand that Alan plans to upload the latest (0.8.5~b4) this weekend. I understand your frustration at the limited expressiveness of Status, and as the lead developer of BLCR I had also complained (in comment #96, the last human-generated comment before yours) that dropping the blcr- dkms from the distribution (to satisfy lib dependencies in other packages w/o rebuilding them) was not a Fix. HOWEVER things have progressed since then and, as I understand it, the acceptance of the BLCR beta into Debian Experimental completely justifies the current Fix Released status. So, if you are in need of a working BLCR your best course of action at this time is NOT to post multiple angry messages to this bug report. Instead, you should contribute to the testing of the Beta release - and report your success or failure here, on the Debian bug system, or on the BLCR mailing list. Sufficient testing is the best way to help this package progress out of Experimental. -Paul -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/804943 Title: blcr kernel module failed to build with kernel 3.0 : configure: error: --with-linux argument '3.0-x' is neither a kernel version string nor a full path To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blcr/+bug/804943/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 804943] Re: blcr kernel module failed to build with kernel 3.0 : configure: error: --with-linux argument '3.0-x' is neither a kernel version string nor a full path
What fix: has been released? As the upsteam maintainer I am not aware of any released support for 3.0 or later kernels in blcr. I am actively working on exactly such support and expect a Beta release of blcr-0.8.5 for testing sometime this week. The only fix detailed in this bug report is to REMOVE the blcr-dkms package, which is NOT a fix for the reported problem blcr kernel module failed to build Installing Windows 8 fixes the problem in the same manner, but I don't see that as a recommended course of action. Alan Woodland's release of blcr-0.8.4-3 in Debian is also not a fix as it just drops the blcr-dkms package build from the source package. The remaining packages built from the blcr source package now do NOTHING useful except to satisfy a link dependency from some other packages - but cannot provide the intended FUNCTIONALITY without the kernel module. -Paul -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/804943 Title: blcr kernel module failed to build with kernel 3.0 : configure: error: --with-linux argument '3.0-x' is neither a kernel version string nor a full path To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blcr/+bug/804943/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1086475] Re: Sync blcr 0.8.4-3 (universe) from Debian Unstable (universe)
Benjamin, Thanks for the testing. I don't have any commit access, though as BLCR's upstream I've committed the patch to our repository for inclusion in the next release. Hopefully you or Alan Woodland can commit the patch. -Paul -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1086475 Title: Sync blcr 0.8.4-3 (universe) from Debian Unstable (universe) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blcr/+bug/1086475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1086475] Re: Sync blcr 0.8.4-3 (universe) from Debian Unstable (universe)
Ahh... I see the real problem now: The standard-specified type is siginfo_t, not struct siginfo, though that has *historically* been correct with glibc and is still the type on the kernel side of the interface. I think the include of stddef.h is proper, even if it is not the key issue here, and suggest keeping it. So, I suggest trying the following patch INSTEAD of the previous one: --- blcr-0.8.4/configure.ac 11 Oct 2011 22:11:37 - 1.410.2.39 +++ blcr-0.8.4/configure.ac 10 Dec 2012 03:50:04 - @@ -593,8 +593,9 @@ CR_DEFINE_INT(CR_ASM_CHECKPOINT_OMIT, [CR_CHECKPOINT_OMIT], [#include blcr_common.h.in]) # ICK! CR_DEFINE_INT(CR_ASM_SI_PID_OFFSET, - [offsetof(struct siginfo, si_pid)], + [offsetof(siginfo_t, si_pid)], [#include signal.h +#include stddef.h #ifndef offsetof #define offsetof(TYPE, MEMBER) ((unsigned long) ((TYPE *)0)-MEMBER) #endif]) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1086475 Title: Sync blcr 0.8.4-3 (universe) from Debian Unstable (universe) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blcr/+bug/1086475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1086475] Re: Sync blcr 0.8.4-3 (universe) from Debian Unstable (universe)
The error in comment #5 above is somewhat suspicious. The symbol CR_ASM_SI_PID_OFFSET is a preprocessor define in the configure-generated blcr_config.h. Therefore a small literal integer (such as 12 or 16) should have been expanded in place of this token, and there should be no symbol left for the relocation the linker is complaining about. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1086475 Title: Sync blcr 0.8.4-3 (universe) from Debian Unstable (universe) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blcr/+bug/1086475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1086475] Re: Sync blcr 0.8.4-3 (universe) from Debian Unstable (universe)
The log attached by bdrung contains the following: checking for value for CR_ASM_SI_PID_OFFSET... not found for both the 64- and 32-bit library configuration steps. This explains how the suspicious linker failure is possible (no #define in blcr_config.h). This presumably means that there is no longer an si_pid member in struct siginfo (which would be unlikely given that it is part of the X/Open standard), or that some other issue has prevented the configure probe from locating it. Is it possible to get the config.log, or at least the section of it with the failed CR_ASM_SI_PID_OFFSET probe? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1086475 Title: Sync blcr 0.8.4-3 (universe) from Debian Unstable (universe) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blcr/+bug/1086475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1086475] Re: Sync blcr 0.8.4-3 (universe) from Debian Unstable (universe)
Following up on my own comment with an educated guess: I can see looking at the generated configure script that the compiler might be seeing multiple #defines for offsetof() when including stdio.h and stdlib.h as part of the autoconf macro boilerplate. That could result in a failure to compile the configure probe. If that is the case, then the following 1-line addition might be the fix: --- blcr-0.8.4/configure.ac 11 Oct 2011 22:11:37 - 1.410.2.39 +++ blcr-0.8.4/configure.ac 8 Dec 2012 00:28:18 - @@ -595,6 +595,7 @@ CR_DEFINE_INT(CR_ASM_CHECKPOINT_OMIT, CR_DEFINE_INT(CR_ASM_SI_PID_OFFSET, [offsetof(struct siginfo, si_pid)], [#include signal.h +#include stddef.h #ifndef offsetof #define offsetof(TYPE, MEMBER) ((unsigned long) ((TYPE *)0)-MEMBER) #endif]) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1086475 Title: Sync blcr 0.8.4-3 (universe) from Debian Unstable (universe) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blcr/+bug/1086475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 534175] Re: package blcr-dkms 0.8.2-9 failed to install/upgrade: blcr kernel module failed to build against linux-rt kernel
Hello from upstream. The DKMS log shows checking kernel symbol table for __put_task_struct... configure: error: Found symbol __put_task_struct but no declaration -- please file a bug report. This says the symbol WAS found. So the problem is not a rename, but a missing or relocated prototype. This should be easier to resolve than if the symbol had been removed. However, since configure stops at the first error, I cannot be sure there are no additional, possibly harder to fix, errors lurking after this one. So that I may take a look at this directly (rather posting a potentially long iteration of patches), could somebody please clue me in on what I need to do to get a copy of the relevant linux-rt kernel sources on my Karmic/x86_64 machine. Thanks, -Paul (BLCR -- package blcr-dkms 0.8.2-9 failed to install/upgrade: blcr kernel module failed to build against linux-rt kernel https://bugs.launchpad.net/bugs/534175 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 534175] Re: package blcr-dkms 0.8.2-9 failed to install/upgrade: blcr kernel module failed to build against linux-rt kernel
For the record: I can reproduce w/ the 2.6.31-9-rt kernel in karmic, and I am pursuing the problem there. So, one may ignore my request (in the previous comment) for help getting the Lucid kernel sources. -Paul -- package blcr-dkms 0.8.2-9 failed to install/upgrade: blcr kernel module failed to build against linux-rt kernel https://bugs.launchpad.net/bugs/534175 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 534175] Re: package blcr-dkms 0.8.2-9 failed to install/upgrade: blcr kernel module failed to build against linux-rt kernel
Using the karmic -rt kernel headers I can confirm that this is the only symbol causing configure-time problems. The one-line patch below is sufficient to resolve that issue. However, there are also non-trivial changes in linux/semaphore.h that break things at compile time and will take some time to sort out. diff -u -r1.410.2.13 configure.ac --- configure.ac19 Dec 2009 00:55:46 - 1.410.2.13 +++ configure.ac8 Mar 2010 18:31:08 - @@ -986,7 +986,7 @@ fi # put_task_struct() requires one of these: -CR_FIND_KSYM([__put_task_struct],[CODE]) +CR_FIND_KSYM([__put_task_struct],[CODE],[extern void __put_task_struct(struct task_struct *);]) CR_FIND_KSYM([__put_task_struct_cb],[CODE]) CR_CHECK_KERNEL_MEMBER([mm.task_size],[#include linux/sched.h], -- package blcr-dkms 0.8.2-9 failed to install/upgrade: blcr kernel module failed to build against linux-rt kernel https://bugs.launchpad.net/bugs/534175 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 534175] Re: package blcr-dkms 0.8.2-9 failed to install/upgrade: blcr kernel module failed to build against linux-rt kernel
OK, that was not as bad as I had feared. This attachment makes two minor changes to BLCR that are sufficient for me to manually (e.g. not using DKMS) configure and build for the linux-2.6.31-9-rt kernel for Karmic/x86_64. These changes are such that I think it highly unlikely to break any other builds, though I have tried only compiling for the 2.6.31-9-rt and 2.6.31-16-generic kernels (in Karmic/x86_64). Note that I have only RUN the resulting kernel modules with 2.6.31-16-generic. It would be helpful if the original reporter could apply this patch and verify that BLCR runs correctly with the -rt kernel. Since the -rt kernel is significantly different from -generic, and neither Alan nor I have looked at the -rt kernels before, there does exist the possibility that BLCR could compile fine but could fail at runtime (perhaps as badly as a kernel Oops or lock-up, so be careful). I would encourage Alan to wait for confirmation that this patch results in non-crashing BLCR kernel modules before pushing this patch to debian- unstable. It is my opinion that failing to configure/build is preferable to building a kernel module that crashes. -Paul (the primary BLCR developer) ** Attachment added: patch01a http://launchpadlibrarian.net/40519615/patch01a -- package blcr-dkms 0.8.2-9 failed to install/upgrade: blcr kernel module failed to build against linux-rt kernel https://bugs.launchpad.net/bugs/534175 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 531255] Re: package blcr-dkms 0.8.2-9 failed to install/upgrade: blcr kernel module failed to build - Segmentation fault (core dumped)
The DKMSBuildLog.txt appears to show gcc (or maybe make?) experiencing a SIGSEGV. This is not something that changes to the BLCR kernel module are likely to fix. I suggest that you first ensure that the gcc and make packages are up- to-date. -Paul (the primary BLCR developer) -- package blcr-dkms 0.8.2-9 failed to install/upgrade: blcr kernel module failed to build - Segmentation fault (core dumped) https://bugs.launchpad.net/bugs/531255 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 534175] Re: package blcr-dkms 0.8.2-9 failed to install/upgrade: blcr kernel module failed to build against linux-rt kernel
Alan said Seems odd that it would end up missing those macros. For the curious: At about 2.6.26 the type struct mutex was replaced by struct semaphore, and the various mutex-related functions and macros were implemented in terms of wrappers around the semaphore code. These wrappers still exist today in the vanilla 2.6.33 kernel. However, it looks as if the -rt kernel is in the midst of a translation from struct semaphore to struct anon_semaphore. It has implemented the semaphore functions and macros in terms of the anon_semaphore versions. It appears that the support for the mutex wrappers have been removed in that process. Since BLCR aims to support kernels including those older than 2.6.26, we rely on the mutex wrappers rather than shifting our code to use the semaphore calls. The patch to cr_module/cr_kcompat.h simply reintroduces the 2 missing wrappers that we use. -- package blcr-dkms 0.8.2-9 failed to install/upgrade: blcr kernel module failed to build against linux-rt kernel https://bugs.launchpad.net/bugs/534175 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 534175] Re: package blcr-dkms 0.8.2-9 failed to install/upgrade: blcr kernel module failed to build against linux-rt kernel
pablomme, I am unsure from your comment if you actually used the blcr kernel modules, or just loaded them? If you only loaded them, then I suggest testing them via make insmod check from the blcr build directory. You should be cautious in case the kernel crashes (unlikely, but not impossible). -Paul -- package blcr-dkms 0.8.2-9 failed to install/upgrade: blcr kernel module failed to build against linux-rt kernel https://bugs.launchpad.net/bugs/534175 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 534175] Re: package blcr-dkms 0.8.2-9 failed to install/upgrade: blcr kernel module failed to build against linux-rt kernel
pablomme, Sorry to cause some confusion. I had not considered that the debian/ubuntu packaging for BLCR splits the kernel modules off into a DKMS package. Because of that split, the build directory you are using contains no test codes. So, it would be great if you could build from the debian blcr source package and then make check after using modprobe to load the blcr module you build via DKMS. Alan, In the future, would you consider packaging the blcr-testsuite as is done in the RPM packaging? It greatly simplifies situations like the present one. -Paul -- package blcr-dkms 0.8.2-9 failed to install/upgrade: blcr kernel module failed to build against linux-rt kernel https://bugs.launchpad.net/bugs/534175 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 534175] Re: package blcr-dkms 0.8.2-9 failed to install/upgrade: blcr kernel module failed to build against linux-rt kernel
pablomme, Thanks for the good news! Now, somebody needs to answer Alan's concern (comment #12) of how we might get this into the Lucid release: Alan is the Debian maintainer for the blcr package, but if he commits changes there they may not make it into Lucid this late, right? -Paul -- package blcr-dkms 0.8.2-9 failed to install/upgrade: blcr kernel module failed to build against linux-rt kernel https://bugs.launchpad.net/bugs/534175 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
