[opensuse-buildservice] New kernel module build failures
Some of my device drivers have stop building on OBS (e.g., openSUSE 11.2, 11,3). The log from OBS says this: Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.2QBwE1 + umask 022 + cd /usr/src/packages/BUILD + /bin/rm -rf /usr/src/packages/BUILDROOT/vmic_enable-0.10-10.2.i386 ++ dirname /usr/src/packages/BUILDROOT/vmic_enable-0.10-10.2.i386 + /bin/mkdir -p /usr/src/packages/BUILDROOT + /bin/mkdir /usr/src/packages/BUILDROOT/vmic_enable-0.10-10.2.i386 + cd vmic_enable-0.10 + for flavor in debug default desktop pae xen + rm -rf obj/debug + cp -r source obj/debug + make -C /usr/src/linux-obj/i586/debug modules M=/usr/src/packages/BUILD/vmic_enable-0.10/obj/debug make: Entering directory `/usr/src/linux-2.6.31.5-0.1-obj/i386/debug' Makefile:23: *** mixed implicit and normal rules. Stop. make: Leaving directory `/usr/src/linux-2.6.31.5-0.1-obj/i386/debug' error: Bad exit status from /var/tmp/rpm-tmp.2QBwE1 (%build) All the other repos seem to build as expected. The modules have a Kbuild file, like this: obj-m := vmic_enable.o and a source file. The packages are old, the error is new. Did I miss some change? Yours sincerely, Roger Oberholtzer OPQ Systems / Ramböll RST Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hi,
On 3/18/2011 at 06:44 AM, in message <1300452271.5155.43.camel@acme.pacific>, Roger Oberholtzer <roger@opq.se> wrote: Some of my device drivers have stop building on OBS (e.g., openSUSE 11.2, 11,3). The log from OBS says this:
Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.2QBwE1 + umask 022 + cd /usr/src/packages/BUILD + /bin/rm -rf /usr/src/packages/BUILDROOT/vmic_enable-0.10-10.2.i386 ++ dirname /usr/src/packages/BUILDROOT/vmic_enable-0.10-10.2.i386 + /bin/mkdir -p /usr/src/packages/BUILDROOT + /bin/mkdir /usr/src/packages/BUILDROOT/vmic_enable-0.10-10.2.i386 + cd vmic_enable-0.10 + for flavor in debug default desktop pae xen + rm -rf obj/debug + cp -r source obj/debug + make -C /usr/src/linux-obj/i586/debug modules M=/usr/src/packages/BUILD/vmic_enable-0.10/obj/debug make: Entering directory `/usr/src/linux-2.6.31.5-0.1-obj/i386/debug' Makefile:23: *** mixed implicit and normal rules. Stop. make: Leaving directory `/usr/src/linux-2.6.31.5-0.1-obj/i386/debug' error: Bad exit status from /var/tmp/rpm-tmp.2QBwE1 (%build)
All the other repos seem to build as expected.
The modules have a Kbuild file, like this:
obj-m := vmic_enable.o
and a source file. The packages are old, the error is new. Did I miss some change?
I found some info on the web indicating that this error arises from newer versions of make ( http://www.linuxquestions.org/questions/linux-software-2/error-mixed-implici... ). Perhaps there was an update to the make package in the 11.x repos? Regards, Ann
Yours sincerely,
Roger Oberholtzer
OPQ Systems / Ramböll RST
Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________
Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Fri, Mar 18, 2011 at 11:44 PM, Roger Oberholtzer <roger@opq.se> wrote:
Some of my device drivers have stop building on OBS (e.g., openSUSE 11.2, 11,3). The log from OBS says this:
Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.2QBwE1 + umask 022 + cd /usr/src/packages/BUILD + /bin/rm -rf /usr/src/packages/BUILDROOT/vmic_enable-0.10-10.2.i386 ++ dirname /usr/src/packages/BUILDROOT/vmic_enable-0.10-10.2.i386 + /bin/mkdir -p /usr/src/packages/BUILDROOT + /bin/mkdir /usr/src/packages/BUILDROOT/vmic_enable-0.10-10.2.i386 + cd vmic_enable-0.10 + for flavor in debug default desktop pae xen + rm -rf obj/debug + cp -r source obj/debug + make -C /usr/src/linux-obj/i586/debug modules M=/usr/src/packages/BUILD/vmic_enable-0.10/obj/debug make: Entering directory `/usr/src/linux-2.6.31.5-0.1-obj/i386/debug' Makefile:23: *** mixed implicit and normal rules. Stop. make: Leaving directory `/usr/src/linux-2.6.31.5-0.1-obj/i386/debug' error: Bad exit status from /var/tmp/rpm-tmp.2QBwE1 (%build)
All the other repos seem to build as expected.
The modules have a Kbuild file, like this:
obj-m := vmic_enable.o
and a source file. The packages are old, the error is new. Did I miss some change?
Yours sincerely,
Roger Oberholtzer
OPQ Systems / Ramböll RST
Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________
Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
-- ==================================== FENG Qian Dept. of Automation, Tsinghua Univ. 100084, Beijing, P.R.China ==================================== -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Freitag, 18. März 2011, 13:44:31 schrieb Roger Oberholtzer:
Some of my device drivers have stop building on OBS (e.g., openSUSE 11.2, 11,3). The log from OBS says this:
Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.2QBwE1 + umask 022 + cd /usr/src/packages/BUILD + /bin/rm -rf /usr/src/packages/BUILDROOT/vmic_enable-0.10-10.2.i386 ++ dirname /usr/src/packages/BUILDROOT/vmic_enable-0.10-10.2.i386 + /bin/mkdir -p /usr/src/packages/BUILDROOT + /bin/mkdir /usr/src/packages/BUILDROOT/vmic_enable-0.10-10.2.i386 + cd vmic_enable-0.10 + for flavor in debug default desktop pae xen + rm -rf obj/debug + cp -r source obj/debug + make -C /usr/src/linux-obj/i586/debug modules M=/usr/src/packages/BUILD/vmic_enable-0.10/obj/debug make: Entering directory `/usr/src/linux-2.6.31.5-0.1-obj/i386/debug' Makefile:23: *** mixed implicit and normal rules. Stop. make: Leaving directory `/usr/src/linux-2.6.31.5-0.1-obj/i386/debug' error: Bad exit status from /var/tmp/rpm-tmp.2QBwE1 (%build)
All the other repos seem to build as expected.
The modules have a Kbuild file, like this:
obj-m := vmic_enable.o
and a source file. The packages are old, the error is new. Did I miss some change?
The OBS mailing list is not the best place, better ask kernel developers. -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Mon, 2011-03-21 at 07:44 +0100, Adrian Schröter wrote:
Am Freitag, 18. März 2011, 13:44:31 schrieb Roger Oberholtzer:
Some of my device drivers have stop building on OBS (e.g., openSUSE 11.2, 11,3). The log from OBS says this:
Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.2QBwE1 + umask 022 + cd /usr/src/packages/BUILD + /bin/rm -rf /usr/src/packages/BUILDROOT/vmic_enable-0.10-10.2.i386 ++ dirname /usr/src/packages/BUILDROOT/vmic_enable-0.10-10.2.i386 + /bin/mkdir -p /usr/src/packages/BUILDROOT + /bin/mkdir /usr/src/packages/BUILDROOT/vmic_enable-0.10-10.2.i386 + cd vmic_enable-0.10 + for flavor in debug default desktop pae xen + rm -rf obj/debug + cp -r source obj/debug + make -C /usr/src/linux-obj/i586/debug modules M=/usr/src/packages/BUILD/vmic_enable-0.10/obj/debug make: Entering directory `/usr/src/linux-2.6.31.5-0.1-obj/i386/debug' Makefile:23: *** mixed implicit and normal rules. Stop. make: Leaving directory `/usr/src/linux-2.6.31.5-0.1-obj/i386/debug' error: Bad exit status from /var/tmp/rpm-tmp.2QBwE1 (%build)
All the other repos seem to build as expected.
The modules have a Kbuild file, like this:
obj-m := vmic_enable.o
and a source file. The packages are old, the error is new. Did I miss some change?
The OBS mailing list is not the best place, better ask kernel developers.
I think it is in fact an OBS issue. It is only there that it fails, and only for a few OS versions. The error makes reference to a Makefile. As I use the Kbuild approach (it is an out-of-source-tree kernel module compile), any Makefile is with the kernel as set up in OBS for the build. In this case, in whatever OBS arranges to have in /usr/src/linux-2.6.31.5-0.1-obj/i386/debug. The choice to build a 'debug' version of the module is determined by the OBS macro %flavors_to_build, which expands to "debug default desktop pae xen". Yours sincerely, Roger Oberholtzer OPQ Systems / Ramböll RST Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Mon, 2011-03-21 at 08:53 +0100, Roger Oberholtzer wrote:
On Mon, 2011-03-21 at 07:44 +0100, Adrian Schröter wrote:
Am Freitag, 18. März 2011, 13:44:31 schrieb Roger Oberholtzer:
Some of my device drivers have stop building on OBS (e.g., openSUSE 11.2, 11,3). The log from OBS says this:
Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.2QBwE1 + umask 022 + cd /usr/src/packages/BUILD + /bin/rm -rf /usr/src/packages/BUILDROOT/vmic_enable-0.10-10.2.i386 ++ dirname /usr/src/packages/BUILDROOT/vmic_enable-0.10-10.2.i386 + /bin/mkdir -p /usr/src/packages/BUILDROOT + /bin/mkdir /usr/src/packages/BUILDROOT/vmic_enable-0.10-10.2.i386 + cd vmic_enable-0.10 + for flavor in debug default desktop pae xen + rm -rf obj/debug + cp -r source obj/debug + make -C /usr/src/linux-obj/i586/debug modules M=/usr/src/packages/BUILD/vmic_enable-0.10/obj/debug make: Entering directory `/usr/src/linux-2.6.31.5-0.1-obj/i386/debug' Makefile:23: *** mixed implicit and normal rules. Stop. make: Leaving directory `/usr/src/linux-2.6.31.5-0.1-obj/i386/debug' error: Bad exit status from /var/tmp/rpm-tmp.2QBwE1 (%build)
All the other repos seem to build as expected.
The modules have a Kbuild file, like this:
obj-m := vmic_enable.o
and a source file. The packages are old, the error is new. Did I miss some change?
The OBS mailing list is not the best place, better ask kernel developers.
I think it is in fact an OBS issue. It is only there that it fails, and only for a few OS versions. The error makes reference to a Makefile. As I use the Kbuild approach (it is an out-of-source-tree kernel module compile), any Makefile is with the kernel as set up in OBS for the build. In this case, in whatever OBS arranges to have in /usr/src/linux-2.6.31.5-0.1-obj/i386/debug. The choice to build a 'debug' version of the module is determined by the OBS macro %flavors_to_build, which expands to "debug default desktop pae xen".
I see that this is not limited to one out-of-source-tree kernel module compile. It is all of them. These work: RedHat_RHEL-6 SLE_11_SP1 openSUSE_11.2_Update openSUSE_11.3_Update openSUSE_11.4 openSUSE_Factory These do not: openSUSE_11.2 openSUSE_11.3 If it was a problem in the source for the driver, I would think it very very odd that is only fails for these two repos. It looks to me like something has been updated in 11.4, and the various Update repos for older releases, and a change has been made in OBS to match. The original 11.2 and 11.3 repos contain something older that no longer works with OBS. Anyone else know of any other out-of-kernel drivers in OBS that are working for these two failed-for-me repos? You may need to trigger a rebuild to see the failure. Yours sincerely, Roger Oberholtzer OPQ Systems / Ramböll RST Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Dienstag, 22. März 2011, 09:01:38 schrieb Roger Oberholtzer:
On Mon, 2011-03-21 at 08:53 +0100, Roger Oberholtzer wrote:
On Mon, 2011-03-21 at 07:44 +0100, Adrian Schröter wrote:
Am Freitag, 18. März 2011, 13:44:31 schrieb Roger Oberholtzer:
Some of my device drivers have stop building on OBS (e.g., openSUSE 11.2, 11,3). The log from OBS says this:
Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.2QBwE1 + umask 022 + cd /usr/src/packages/BUILD + /bin/rm -rf /usr/src/packages/BUILDROOT/vmic_enable-0.10-10.2.i386 ++ dirname /usr/src/packages/BUILDROOT/vmic_enable-0.10-10.2.i386 + /bin/mkdir -p /usr/src/packages/BUILDROOT + /bin/mkdir /usr/src/packages/BUILDROOT/vmic_enable-0.10-10.2.i386 + cd vmic_enable-0.10 + for flavor in debug default desktop pae xen + rm -rf obj/debug + cp -r source obj/debug + make -C /usr/src/linux-obj/i586/debug modules M=/usr/src/packages/BUILD/vmic_enable-0.10/obj/debug make: Entering directory `/usr/src/linux-2.6.31.5-0.1-obj/i386/debug' Makefile:23: *** mixed implicit and normal rules. Stop. make: Leaving directory `/usr/src/linux-2.6.31.5-0.1-obj/i386/debug' error: Bad exit status from /var/tmp/rpm-tmp.2QBwE1 (%build)
All the other repos seem to build as expected.
The modules have a Kbuild file, like this:
obj-m := vmic_enable.o
and a source file. The packages are old, the error is new. Did I miss some change?
The OBS mailing list is not the best place, better ask kernel developers.
I think it is in fact an OBS issue. It is only there that it fails, and only for a few OS versions. The error makes reference to a Makefile. As I use the Kbuild approach (it is an out-of-source-tree kernel module compile), any Makefile is with the kernel as set up in OBS for the build. In this case, in whatever OBS arranges to have in /usr/src/linux-2.6.31.5-0.1-obj/i386/debug. The choice to build a 'debug' version of the module is determined by the OBS macro %flavors_to_build, which expands to "debug default desktop pae xen".
I see that this is not limited to one out-of-source-tree kernel module compile. It is all of them. These work:
RedHat_RHEL-6
SLE_11_SP1
openSUSE_11.2_Update
openSUSE_11.3_Update
openSUSE_11.4
openSUSE_Factory
These do not:
openSUSE_11.2
openSUSE_11.3
If it was a problem in the source for the driver, I would think it very very odd that is only fails for these two repos. It looks to me like something has been updated in 11.4, and the various Update repos for older releases, and a change has been made in OBS to match. The original 11.2 and 11.3 repos contain something older that no longer works with OBS.
Anyone else know of any other out-of-kernel drivers in OBS that are working for these two failed-for-me repos? You may need to trigger a rebuild to see the failure.
It is still unlikely that any "OBS change" has caused this. All the used macros and scripts are provided via packages. And OBS would behave in the same way for all repos. So, you need to debug the kernel build enviroment, sorry, I can't help you here. -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Tue, 2011-03-22 at 09:11 +0100, Adrian Schröter wrote:
I see that this is not limited to one out-of-source-tree kernel module compile. It is all of them. These work:
RedHat_RHEL-6
SLE_11_SP1
openSUSE_11.2_Update
openSUSE_11.3_Update
openSUSE_11.4
openSUSE_Factory
These do not:
openSUSE_11.2
openSUSE_11.3
If it was a problem in the source for the driver, I would think it very very odd that is only fails for these two repos. It looks to me like something has been updated in 11.4, and the various Update repos for older releases, and a change has been made in OBS to match. The original 11.2 and 11.3 repos contain something older that no longer works with OBS.
Anyone else know of any other out-of-kernel drivers in OBS that are working for these two failed-for-me repos? You may need to trigger a rebuild to see the failure.
It is still unlikely that any "OBS change" has caused this. All the used macros and scripts are provided via packages. And OBS would behave in the same way for all repos.
So, you need to debug the kernel build enviroment, sorry, I can't help you here.
Isn't it OBS that sets that up? It is OBS that chooses a kernel source from somewhere and puts it in the build. I do not provide that in the build. The Makefile that is being complained about does not come from anything I provide. It must be triggered by these statements in my spec: BuildRequires: %kernel_module_package_buildreqs %kernel_module_package A sample spec is: https://build.opensuse.org/package/view_file?file=universe.spec&package=universe&project=home%3Arogeroberholtzer&srcmd5=c1e7d331a7f0803ada9e50afd57c9743 This spec works on all but two repos in OBS. It worked for those repos up to about a month ago. Then is started failing. And only for these repos. Yours sincerely, Roger Oberholtzer OPQ Systems / Ramböll RST Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Dienstag, 22. März 2011, 09:36:37 schrieb Roger Oberholtzer:
On Tue, 2011-03-22 at 09:11 +0100, Adrian Schröter wrote:
I see that this is not limited to one out-of-source-tree kernel module compile. It is all of them. These work:
RedHat_RHEL-6
SLE_11_SP1
openSUSE_11.2_Update
openSUSE_11.3_Update
openSUSE_11.4
openSUSE_Factory
These do not:
openSUSE_11.2
openSUSE_11.3
If it was a problem in the source for the driver, I would think it very very odd that is only fails for these two repos. It looks to me like something has been updated in 11.4, and the various Update repos for older releases, and a change has been made in OBS to match. The original 11.2 and 11.3 repos contain something older that no longer works with OBS.
Anyone else know of any other out-of-kernel drivers in OBS that are working for these two failed-for-me repos? You may need to trigger a rebuild to see the failure.
It is still unlikely that any "OBS change" has caused this. All the used macros and scripts are provided via packages. And OBS would behave in the same way for all repos.
So, you need to debug the kernel build enviroment, sorry, I can't help you here.
Isn't it OBS that sets that up? It is OBS that chooses a kernel source from somewhere and puts it in the build. I do not provide that in the build. The Makefile that is being complained about does not come from anything I provide.
It must be triggered by these statements in my spec:
BuildRequires: %kernel_module_package_buildreqs
We don't support macros as build requires, it would mean that the scheduler would need to setup a build enviroment to calculate the packages for the build enviroment ;) That can't really work, you can try to workaround this by defining/replacing this definition in prjconf to a fixed set of packages. Optionally also different for each of your repositories.
%kernel_module_package
A sample spec is:
This spec works on all but two repos in OBS. It worked for those repos up to about a month ago. Then is started failing. And only for these repos.
If that ever worked, it was just luck.
Yours sincerely,
Roger Oberholtzer
OPQ Systems / Ramböll RST
Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________
Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se
-- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Tue, 2011-03-22 at 09:43 +0100, Adrian Schröter wrote:
Am Dienstag, 22. März 2011, 09:36:37 schrieb Roger Oberholtzer:
Isn't it OBS that sets that up? It is OBS that chooses a kernel source from somewhere and puts it in the build. I do not provide that in the build. The Makefile that is being complained about does not come from anything I provide.
It must be triggered by these statements in my spec:
BuildRequires: %kernel_module_package_buildreqs
We don't support macros as build requires, it would mean that the scheduler would need to setup a build enviroment to calculate the packages for the build enviroment ;)
That can't really work, you can try to workaround this by defining/replacing this definition in prjconf to a fixed set of packages. Optionally also different for each of your repositories.
%kernel_module_package
A sample spec is:
This spec works on all but two repos in OBS. It worked for those repos up to about a month ago. Then is started failing. And only for these repos.
If that ever worked, it was just luck.
Now I am really confused. I did not make up these macros. But perhaps they are old and OBS has moved on. And perhaps the BuildRequires is really doing nothing. Perhaps it is the %kernel_module_package statement that is really doing something. Could you point me to a sample that implements kernel module building as is "should" be implemented? I have looked at, say, the nvidia spec. I am confused why they have a lot of references hardwired and not via some OBS macro. For example, that spec has: for flavor in %flavors_to_build; do make -C /usr/src/linux-obj/%_target_cpu/$flavor modules_install M=$PWD/obj/$flavor/%{version} when I am using (successfully...): for flavor in %flavors_to_build; do make -C %{kernel_source $flavor} modules_install M=$PWD/obj/$flavor It is the -C syntax. I am using things that come from OBS. Why doesn't the nvidia spec do so? Is it just preference, or is there some legitimate reason? I am more than happy to do what OBS requires. It is just that it is unclear to me what that might be. Yours sincerely, Roger Oberholtzer OPQ Systems / Ramböll RST Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hi,
On 3/22/2011 at 03:14 AM, in message <1300785260.8551.91.camel@acme.pacific>, Roger Oberholtzer <roger@opq.se> wrote: On Tue, 2011-03-22 at 09:43 +0100, Adrian Schröter wrote: Am Dienstag, 22. März 2011, 09:36:37 schrieb Roger Oberholtzer:
Isn't it OBS that sets that up? It is OBS that chooses a kernel source from somewhere and puts it in the build. I do not provide that in the build. The Makefile that is being complained about does not come from anything I provide.
It must be triggered by these statements in my spec:
BuildRequires: %kernel_module_package_buildreqs
We don't support macros as build requires, it would mean that the scheduler would need to setup a build enviroment to calculate the packages for the build enviroment ;)
That can't really work, you can try to workaround this by defining/replacing this definition in prjconf to a fixed set of packages. Optionally also different for each of your repositories.
%kernel_module_package
A sample spec is:
https://build.opensuse.org/package/view_file?file=universe.spec&package=univer se&project=home%3Arogeroberholtzer&srcmd5=c1e7d331a7f0803ada9e50
afd57c9743
This spec works on all but two repos in OBS. It worked for those repos up to about a month ago. Then is started failing. And only for these repos.
If that ever worked, it was just luck.
Now I am really confused. I did not make up these macros. But perhaps they are old and OBS has moved on. And perhaps the BuildRequires is really doing nothing. Perhaps it is the %kernel_module_package statement that is really doing something.
Could you point me to a sample that implements kernel module building as is "should" be implemented? I have looked at, say, the nvidia spec. I am confused why they have a lot of references hardwired and not via some OBS macro. For example, that spec has:
for flavor in %flavors_to_build; do make -C /usr/src/linux-obj/%_target_cpu/$flavor modules_install M=$PWD/obj/$flavor/%{version}
when I am using (successfully...):
for flavor in %flavors_to_build; do make -C %{kernel_source $flavor} modules_install M=$PWD/obj/$flavor
It is the -C syntax. I am using things that come from OBS. Why doesn't the nvidia spec do so? Is it just preference, or is there some legitimate reason?
I am more than happy to do what OBS requires. It is just that it is unclear to me what that might be.
Pls. take a look at the project/package home:andavis:novell-hello; it's a very simple KMP that uses the macros and is building successfully for opensuse 11.x. The Kernel Module Packages Manuals ( http://www.novell.com/developer/kernel_module_packages_manuals.html ) specifies to use the macros so certainly OBS should be able to handle them. They have always worked for SLE 11 SP1. Regards, Ann
Yours sincerely,
Roger Oberholtzer
OPQ Systems / Ramböll RST
Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________
Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Tue, 2011-03-22 at 08:58 -0600, Ann Davis wrote:
Pls. take a look at the project/package home:andavis:novell-hello; it's a very simple KMP that uses the macros and is building successfully for opensuse 11.x.
The Kernel Module Packages Manuals ( http://www.novell.com/developer/kernel_module_packages_manuals.html ) specifies to use the macros so certainly OBS should be able to handle them. They have always worked for SLE 11 SP1.
I must have used that as a guide when I made my spec files. The spec file there is almost identical to mine. With one exception. I have: %kernel_module_package and the sample has: %kernel_module_package -x debug -x trace So, I added those options as well. My Kbuild file is a standard one: obj-m := vmic_enable.o The module is one source file: vmic_enable.c Of course with these options the error persist. But I see a bit more:
From the OBS log, I see this for the working novell-hello driver:
+ exec rpmbuild -ba --define '_srcdefattr (-,root,root)' --define 'disturl obs://build.opensuse.org/home:andavis/openSUSE_11.2/136e91aafca2d76ed4550af5141b092e-novell-hello' /usr/src/packages/SOURCES/novell-hello.spec Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.DpWpV3 + umask 022 For my not working vmic_enable driver I see this: + exec rpmbuild -ba --define '_srcdefattr (-,root,root)' --define 'disturl obs://build.opensuse.org/home:rogeroberholtzer/openSUSE_11.2/e26b2630e283fef1ba4bf28da64b7b66-vmic_enable' /usr/src/packages/SOURCES/vmic_enable.spec Makefile:23: *** mixed implicit and normal rules. Stop. Makefile:23: *** mixed implicit and normal rules. Stop. Makefile:23: *** mixed implicit and normal rules. Stop. Makefile:23: *** mixed implicit and normal rules. Stop. Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.N9vyzX + umask 022 Why? Who's Makefile is this that is not happy? All I provide is the bit of Kbuild as listed above. Surely that is not making the build on only 2 of the repos unhappy. I remain convinced something is up in OBS land. At least when building out-of-tree kernel modules on openSUSE 11.2 and 11.3 (all other repos tried are working). Yours sincerely, Roger Oberholtzer OPQ Systems / Ramböll RST Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Roger,
On 3/23/2011 at 10:36 AM, in message <1300898162.1065.257.camel@acme.pacific>, Roger Oberholtzer <roger@opq.se> wrote: From the OBS log, I see this for the working novell-hello driver:
+ exec rpmbuild -ba --define '_srcdefattr (-,root,root)' --define 'disturl obs://build.opensuse.org/home:andavis/openSUSE_11.2/136e91aafca2d76ed4550af51 41b092e-novell-hello' /usr/src/packages/SOURCES/novell-hello.spec Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.DpWpV3 + umask 022
For my not working vmic_enable driver I see this:
+ exec rpmbuild -ba --define '_srcdefattr (-,root,root)' --define 'disturl obs://build.opensuse.org/home:rogeroberholtzer/openSUSE_11.2/e26b2630e283fef1 ba4bf28da64b7b66-vmic_enable' /usr/src/packages/SOURCES/vmic_enable.spec Makefile:23: *** mixed implicit and normal rules. Stop. Makefile:23: *** mixed implicit and normal rules. Stop. Makefile:23: *** mixed implicit and normal rules. Stop. Makefile:23: *** mixed implicit and normal rules. Stop. Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.N9vyzX + umask 022
I think there may be something very strange in the %description line in your spec file. An octal dump of novell-hello.spec seems to show appropriate octal codes for the string "%description" ( 062045 071545 071143 070151 064564 067157 000012 0000015 ) but the octal dump of vmic_enable.spec does not show these. It kind of makes sense that this area of the spec file is causing the problem, since the failure message occurs right before the %prep section. Anyway, I suggest looking at your existing vmic_enable.spec file using the "od" command and/or manually typing and uploading the whole spec file again... BTW, I also thought it might be a dos2unix thing; I have seen this cause strange behaviors. Otherwise, I'm baffled. Very odd, especially given that it's working on other targets. Regards, Ann -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Wed, 2011-03-23 at 14:33 -0600, Ann Davis wrote:
On 3/23/2011 at 10:36 AM, Roger Oberholtzer <roger@opq.se> wrote: From the OBS log, I see this for the working novell-hello driver:
+ exec rpmbuild -ba --define '_srcdefattr (-,root,root)' --define 'disturl obs://build.opensuse.org/home:andavis/openSUSE_11.2/136e91aafca2d76ed4550af51 41b092e-novell-hello' /usr/src/packages/SOURCES/novell-hello.spec Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.DpWpV3 + umask 022
For my not working vmic_enable driver I see this:
+ exec rpmbuild -ba --define '_srcdefattr (-,root,root)' --define 'disturl obs://build.opensuse.org/home:rogeroberholtzer/openSUSE_11.2/e26b2630e283fef1 ba4bf28da64b7b66-vmic_enable' /usr/src/packages/SOURCES/vmic_enable.spec Makefile:23: *** mixed implicit and normal rules. Stop. Makefile:23: *** mixed implicit and normal rules. Stop. Makefile:23: *** mixed implicit and normal rules. Stop. Makefile:23: *** mixed implicit and normal rules. Stop. Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.N9vyzX + umask 022
I think there may be something very strange in the %description line in your spec file. An octal dump of novell-hello.spec seems to show appropriate octal codes for the string "%description" ( 062045 071545 071143 070151 064564 067157 000012 0000015 ) but the octal dump of vmic_enable.spec does not show these. It kind of makes sense that this area of the spec file is causing the problem, since the failure message occurs right before the %prep section. Anyway, I suggest looking at your existing vmic_enable.spec file using the "od" command and/or manually typing and uploading the whole spec file again...
You can test this really quickly using the iconv command. Try 'iconv -f UTF-8 -t US-ASCII vmic_enable.spec'. This will validate the all the characters are plain 7-bit ASCII. Thanks, Peter -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Wed, 2011-03-23 at 16:46 -0400, Peter Bowen wrote:
u can test this really quickly using the iconv command. Try 'iconv -f UTF-8 -t US-ASCII vmic_enable.spec'. This will validate the all the characters are plain 7-bit ASCII.
Thanks for the tip. It verified what I saw in okteta - all characters are as expected. Too bad. Funny chars can be sorted out. -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 SHAW'S PRINCIPAL Build a system that even a fool can use, and only a fool will want to use it. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hi,
On 3/23/2011 at 03:57 PM, in message <1300917456.11772.9.camel@barracuda.pacific>, Roger Oberholtzer <roger@opq.se> wrote: On Wed, 2011-03-23 at 16:46 -0400, Peter Bowen wrote: u can test this really quickly using the iconv command. Try 'iconv -f UTF-8 -t US-ASCII vmic_enable.spec'. This will validate the all the characters are plain 7-bit ASCII.
Thanks for the tip. It verified what I saw in okteta - all characters are as expected. Too bad. Funny chars can be sorted out.
I linked your home:rogeroberholtzer:vmic_enable package to a new package in my home:andavis project. (I hope that this is the package that's giving you trouble...) Anyway, the one in my home:andavis project builds fine for openSUSE_11.2. ???? Ann
-- Roger Oberholtzer
OPQ Systems / Ramböll RST
Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden
Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696
SHAW'S PRINCIPAL Build a system that even a fool can use, and only a fool will want to use it.
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On 3/23/2011 at 03:31 PM, in message <4D8A124E020000D6000AD467@novprvoes0310.provo.novell.com>, "Ann Davis" <andavis@novell.com> wrote: Hi,
On 3/23/2011 at 03:57 PM, in message <1300917456.11772.9.camel@barracuda.pacific>, Roger Oberholtzer <roger@opq.se> wrote: On Wed, 2011-03-23 at 16:46 -0400, Peter Bowen wrote: u can test this really quickly using the iconv command. Try 'iconv -f UTF-8 -t US-ASCII vmic_enable.spec'. This will validate the all the characters are plain 7-bit ASCII.
Thanks for the tip. It verified what I saw in okteta - all characters are as expected. Too bad. Funny chars can be sorted out.
I linked your home:rogeroberholtzer:vmic_enable package to a new package in my home:andavis project. (I hope that this is the package that's giving you trouble...) Anyway, the one in my home:andavis project builds fine for openSUSE_11.2.
????
Follow-up: I looked at the raw config for your home:rogeroberholtzer project. The openSUSE_11.2 section has some project paths that I think are causing the problem. Regards, Ann
Ann
-- Roger Oberholtzer
OPQ Systems / Ramböll RST
Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden
Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696
SHAW'S PRINCIPAL Build a system that even a fool can use, and only a fool will want to use it.
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Wed, 2011-03-23 at 14:33 -0600, Ann Davis wrote:
Roger,
On 3/23/2011 at 10:36 AM, in message <1300898162.1065.257.camel@acme.pacific>, Roger Oberholtzer <roger@opq.se> wrote: From the OBS log, I see this for the working novell-hello driver:
+ exec rpmbuild -ba --define '_srcdefattr (-,root,root)' --define 'disturl obs://build.opensuse.org/home:andavis/openSUSE_11.2/136e91aafca2d76ed4550af51 41b092e-novell-hello' /usr/src/packages/SOURCES/novell-hello.spec Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.DpWpV3 + umask 022
For my not working vmic_enable driver I see this:
+ exec rpmbuild -ba --define '_srcdefattr (-,root,root)' --define 'disturl obs://build.opensuse.org/home:rogeroberholtzer/openSUSE_11.2/e26b2630e283fef1 ba4bf28da64b7b66-vmic_enable' /usr/src/packages/SOURCES/vmic_enable.spec Makefile:23: *** mixed implicit and normal rules. Stop. Makefile:23: *** mixed implicit and normal rules. Stop. Makefile:23: *** mixed implicit and normal rules. Stop. Makefile:23: *** mixed implicit and normal rules. Stop. Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.N9vyzX + umask 022
I think there may be something very strange in the %description line in your spec file. An octal dump of novell-hello.spec seems to show appropriate octal codes for the string "%description" ( 062045 071545 071143 070151 064564 067157 000012 0000015 ) but the octal dump of vmic_enable.spec does not show these. It kind of makes sense that this area of the spec file is causing the problem, since the failure message occurs right before the %prep section. Anyway, I suggest looking at your existing vmic_enable.spec file using the "od" command and/or manually typing and uploading the whole spec file again...
There are spaces at the end of the description line. The file is 7-bit clean ASCII. I removed all spaces at the end of all lines. Still fails. The thing is that I have three very different drivers that all have the same complaint for these two repos.
BTW, I also thought it might be a dos2unix thing; I have seen this cause strange behaviors.
Otherwise, I'm baffled. Very odd, especially given that it's working on other targets.
Flumexed here, too. -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 SHAW'S PRINCIPAL Build a system that even a fool can use, and only a fool will want to use it. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Wed, 2011-03-23 at 22:56 +0100, Roger Oberholtzer wrote:
On Wed, 2011-03-23 at 14:33 -0600, Ann Davis wrote:
I think there may be something very strange in the %description line in your spec file. An octal dump of novell-hello.spec seems to show appropriate octal codes for the string "%description" ( 062045 071545 071143 070151 064564 067157 000012 0000015 ) but the octal dump of vmic_enable.spec does not show these. It kind of makes sense that this area of the spec file is causing the problem, since the failure message occurs right before the %prep section. Anyway, I suggest looking at your existing vmic_enable.spec file using the "od" command and/or manually typing and uploading the whole spec file again...
Forgot to add that the hex of the string in my file is: 25 64 65 73 63 72 69 70 74 69 6F 6E Which == %description -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 SHAW'S PRINCIPAL Build a system that even a fool can use, and only a fool will want to use it. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On 3/23/2011 at 04:02 PM, in message <1300917754.11772.13.camel@barracuda.pacific>, Roger Oberholtzer <roger@opq.se> wrote:
On Wed, 2011-03-23 at 22:56 +0100, Roger Oberholtzer wrote:
Forgot to add that the hex of the string in my file is:
25 64 65 73 63 72 69 70 74 69 6F 6E
Which == %description
Yeah, I think I was not using od correctly... I can see the %description line using "od -c". The only other difference I noticed was that the novell-hello build output message starts with: Using BUILD_ROOT=/var/cache/obs/worker//root_3/.mount whereas the vmic_enable.spec output says: Using BUILD_ROOT=/var/cache/obs/worker//root_2/.mount Back to an OBS issue? Ann -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (5)
-
Adrian Schröter -
Ann Davis -
Peter Bowen -
Qian Feng -
Roger Oberholtzer