On Tuesday, February 6, 2018 8:50:17 AM EST Sérgio Basto wrote: > On Tue, 2018-02-06 at 08:41 -0500, Steve Grubb wrote: > > On Monday, February 5, 2018 10:06:43 AM EST Petr Viktorin wrote: > > > > I think the basic answer is that the byte comoilation script is > > > > using all sorts of strange heuristics. It seems that it determined a > > > > that a non-python file was python. > > > > > > > > Efforts are under way to redefine things and make the byte > > > > compilation more explicit. Until this is done, this is probably not > > > > the last error of this sort. > > > > > > > > In other words, it's sort of a known bug with fixes under way, > > > > slowly... > > > > > > I'd like to make sure any Python-related automation is limited to > > > Python context (/usr/lib*/python*, files with python shebangs, etc.). > > > I'm not sure why it's not this way now. > > > > > > We're preparing a Change to fix this exact issue in Fedora 29. > > > Started just last week, actually: > > > https://fedoraproject.org/wiki/Changes/No_more_automagic_Python_byt > > > ecompilation > > > > > > Up to this point I thought this was just a theoretical issue. Thank > > > you for finding a concrete example -- and sorry it had to be you! > > > > > > OK. RStudio failing to build was an irritation. Now I have a serious > > problem. The python byte compiler is preventing akmods from building > > kernel modules leaving me with a near unusable system. > > > > 2018/02/06 07:09:32 akmodsbuild: + cd nvidia-kmod-390.25 > > 2018/02/06 07:09:32 akmodsbuild: + for kernel_version in 4.14.16- > > 300.fc27.x86_64___/usr/src/kernels/4.14.16-300.fc27.x86_64 > > 2018/02/06 07:09:32 akmodsbuild: + mkdir -p > > /tmp/akmodsbuild.9LmgJsG6/BUILDROOT/nvidia-kmod-390.25- > > 1.fc27.x86_64//usr/lib/modules//4.14.16- > > 300.fc27.x86_64//extra/nvidia// > > 2018/02/06 07:09:32 akmodsbuild: + install -D -m 0755 > > _kmod_build_4.14.16-300.fc27.x86_64/nvidia-drm.ko > > _kmod_build_4.14.16-300.fc27.x86_64/nvidia-modeset.ko > > _kmod_build_4.14.16-300.fc27.x86_64/nvidia-uvm.ko > > _kmod_build_4.14.16-300.fc27.x86_64/nvidia.ko > > /tmp/akmodsbuild.9LmgJsG6/BUILDROOT/nvidia-kmod-390.25- > > 1.fc27.x86_64//usr/lib/modules//4.14.16- > > 300.fc27.x86_64//extra/nvidia// > > 2018/02/06 07:09:32 akmodsbuild: + /usr/lib/rpm/check-buildroot > > 2018/02/06 07:09:32 akmodsbuild: + /usr/lib/rpm/brp-compress > > 2018/02/06 07:09:32 akmodsbuild: + /usr/lib/rpm/brp-strip > > /usr/bin/strip > > 2018/02/06 07:09:32 akmodsbuild: + /usr/lib/rpm/brp-strip-comment- > > note /usr/bin/strip /usr/bin/objdump > > 2018/02/06 07:09:32 akmodsbuild: + /usr/lib/rpm/brp-strip-static- > > archive /usr/bin/strip > > 2018/02/06 07:09:32 akmodsbuild: + /usr/lib/rpm/brp-python- > > bytecompile /usr/bin/python 1 > > 2018/02/06 07:09:32 akmodsbuild: error: Bad exit status from > > /var/tmp/rpm-tmp.5l5Sxs (%install) > > > > The issue is this, today a new nvidia driver was release via > > rpmfusion. Now my user space does not match kernel modules. Kernel > > modules are failing to build as noted above. When it boots. it detects > > this mismatch and refuses to work. > > > > Is there a way to suppress this to get kernel modules to build? > > hum haven't you a modified version of rpm-build [1] in your computer ? > > [1] rpm -qf /usr/lib/rpm/brp-python-bytecompile -V Nope. The whole package passes verification. [root@x2 ~]# rpm -qV rpm-build-4.14.0-2.fc27.x86_64 [root@x2 ~]# Any way to generate troubleshooting info to help figure out what's wrong? Any good way to suppress this so akmods works? -Steve _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
