[opensuse-packaging] removal help -line: %suse_update_config.
Hello How is the following error fixed: Thanks Glenn Part of log shown below. Full Log see [1] Here is the spec file[2] Question: What can replace this section ? %{?suse_update_config:%{suse_update_config -f}} aclocal --force libtoolize --force autoconf --force autoheader --force automake -afc CFLAGS="$RPM_OPT_FLAGS -Wall -Wno-unused" \ ./configure \ --prefix=%{_prefix} \ --libdir=%{_libdir} \ --bindir=%{_bindir} \ --includedir=%{_includedir} \ --sysconfdir=%{_sysconfdir} \ --mandir=%{_mandir} make %{?jobs:-j%jobs} CFLAGS="$RPM_OPT_FLAGS -Wall -Wno-unused" entire log see [1] https://build.opensuse.org/package/live_build_log?arch=x86_64&package=reiser4progs&project=home%3Adoiggl&repository=openSUSE_12.2 . . [ 58s] + exec rpmbuild -ba --define '_srcdefattr (-,root,root)' --nosignature --define '_build_create_debug 1' --define 'disturl obs://build.opensuse.org/home:doiggl/openSUSE_12.2/cdaef9d019b97ec53d83b9f78cf06d19-reiser4progs' /home/abuild/rpmbuild/SOURCES/reiser4progs.spec [ 58s] Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.XZ0ADg [ 58s] + umask 022 [ 58s] + cd /home/abuild/rpmbuild/BUILD [ 58s] + cd /home/abuild/rpmbuild/BUILD [ 58s] + rm -rf reiser4progs-1.0.7 [ 58s] + /usr/bin/bzip2 -dc /home/abuild/rpmbuild/SOURCES/reiser4progs-1.0.7.tar.bz2 [ 58s] + /bin/tar -xf - [ 59s] + STATUS=0 [ 59s] + '[' 0 -ne 0 ']' [ 59s] + cd reiser4progs-1.0.7 [ 59s] + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w . [ 59s] + echo 'Patch #1 (fsck-dont-allocate-unalloc-extents.patch):' [ 59s] Patch #1 (fsck-dont-allocate-unalloc-extents.patch): [ 59s] + /usr/bin/cat /home/abuild/rpmbuild/SOURCES/fsck-dont-allocate-unalloc-extents.patch [ 59s] + /usr/bin/patch -s -p1 --fuzz=0 [ 59s] + echo 'Patch #2 (reiser4progs-fsck-handle-unprepped-cluster.patch):' [ 59s] Patch #2 (reiser4progs-fsck-handle-unprepped-cluster.patch): [ 59s] + /usr/bin/patch -s -p1 --fuzz=0 [ 59s] + /usr/bin/cat /home/abuild/rpmbuild/SOURCES/reiser4progs-fsck-handle-unprepped-cluster.patch [ 59s] + exit 0 [ 59s] Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.9M0EQf [ 59s] + umask 022 [ 59s] + cd /home/abuild/rpmbuild/BUILD [ 59s] + /usr/bin/rm -rf /home/abuild/rpmbuild/BUILDROOT/reiser4progs-1.0.7-5.1.x86_64 [ 59s] ++ dirname /home/abuild/rpmbuild/BUILDROOT/reiser4progs-1.0.7-5.1.x86_64 [ 59s] + /usr/bin/mkdir -p /home/abuild/rpmbuild/BUILDROOT [ 59s] + /usr/bin/mkdir /home/abuild/rpmbuild/BUILDROOT/reiser4progs-1.0.7-5.1.x86_64 [ 59s] + cd reiser4progs-1.0.7 [ 59s] + echo 'WARNING: REMOVE %suse_update_config. If your sources are really' [ 59s] WARNING: REMOVE %suse_update_config. If your sources are really [ 59s] + echo 'too old to cover current architectures, prefer autoreconf --force --install' [ 59s] too old to cover current architectures, prefer autoreconf --force --install [ 59s] + autoreconf --force --install [ 59s] /var/tmp/rpm-tmp.9M0EQf: line 33: autoreconf: command not found [ 59s] error: Bad exit status from /var/tmp/rpm-tmp.9M0EQf (%build) [ 59s] [ 59s] [ 59s] RPM build errors: [ 59s] Bad exit status from /var/tmp/rpm-tmp.9M0EQf (%build) [ 61s] /.build/build: line 313: 239 Killed background_monitor_process / &>/dev/null [ 63s] [ 49.794059] SysRq : Power Off [ 63s] [ 49.819442] Power down. [2]https://build.opensuse.org/package/view_file?expand=1&file=reiser4progs.spec&package=reiser4progs&project=home%3Adoiggl&rev=cdaef9d019b97ec53d83b9f78cf06d19 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On 11/25/2012 02:30 PM, doiggl@velocitynet.com.au wrote:
Hello
How is the following error fixed: Thanks Glenn
Part of log shown below. Full Log see [1] Here is the spec file[2]
Question: What can replace this section ? %{?suse_update_config:%{suse_update_config -f}} aclocal --force libtoolize --force autoconf --force autoheader --force automake -afc [...]
See below in the warning message:
[ 59s] + echo 'WARNING: REMOVE %suse_update_config. If your sources are really' [ 59s] WARNING: REMOVE %suse_update_config. If your sources are really [ 59s] + echo 'too old to cover current architectures, prefer autoreconf --force --install' [ 59s] too old to cover current architectures, prefer autoreconf --force
so, in your case, just remove the suse_update_config line, it's not needed at all, Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Sun, Nov 25, 2012 at 04:07:50PM +0100, Andreas Jaeger wrote:
On 11/25/2012 02:30 PM, doiggl@velocitynet.com.au wrote:
Hello
How is the following error fixed: Thanks Glenn
Part of log shown below. Full Log see [1] Here is the spec file[2]
Question: What can replace this section ? %{?suse_update_config:%{suse_update_config -f}} aclocal --force libtoolize --force autoconf --force autoheader --force automake -afc [...]
See below in the warning message:
[ 59s] + echo 'WARNING: REMOVE %suse_update_config. If your sources are really' [ 59s] WARNING: REMOVE %suse_update_config. If your sources are really [ 59s] + echo 'too old to cover current architectures, prefer autoreconf --force --install' [ 59s] too old to cover current architectures, prefer autoreconf --force
so, in your case, just remove the suse_update_config line, it's not needed at all,
Actually it might be needed on older software (>5 years) as it will not build stuff for powerpc and other architectures. But usally not. We had to fix 3 - 5 packages for power after this removal. Ciao, Marcus -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Mon, Nov 26, 2012 at 12:30:20AM +1100, doiggl@velocitynet.com.au wrote:
Hello
How is the following error fixed: Thanks Glenn
Part of log shown below. Full Log see [1] Here is the spec file[2]
Question: What can replace this section ? %{?suse_update_config:%{suse_update_config -f}}
You can first remove it completely and see if anything breaks. If nothing break ... nothing else to do. If stuff breaks, you can add "autoconf" to the BuildRequires and run autoconf and friends. Ciao, Marcus -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Am Sonntag, 25. November 2012, 16:50:35 schrieb Marcus Meissner:
On Mon, Nov 26, 2012 at 12:30:20AM +1100, doiggl@velocitynet.com.au wrote:
Hello
How is the following error fixed: Thanks Glenn
Part of log shown below. Full Log see [1] Here is the spec file[2]
Question: What can replace this section ? %{?suse_update_config:%{suse_update_config -f}}
You can first remove it completely and see if anything breaks.
If nothing break ... nothing else to do.
If stuff breaks, you can add "autoconf" to the BuildRequires and run autoconf and friends.
An upcoming aarch64 port might need this line back again though ... Dunno if it makes sense to remove it atm. -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Sun, 25 Nov 2012 16:50:35 +0100, Marcus Meissner <meissner@suse.de> wrote:
On Mon, Nov 26, 2012 at 12:30:20AM +1100, doiggl@velocitynet.com.au wrote:
Hello
How is the following error fixed: Thanks Glenn
Part of log shown below. Full Log see [1] Here is the spec file[2]
Question: What can replace this section ? %{?suse_update_config:%{suse_update_config -f}}
You can first remove it completely and see if anything breaks.
If nothing break ... nothing else to do.
If stuff breaks, you can add "autoconf" to the BuildRequires and run autoconf and friends.
Ciao, Marcus
Hello Question: How can I remove the %suse_update_config part without breaking the entire %build section, What should the new line(s) look like. The old %build section of the .spec reads as %build %{?suse_update_config:%{suse_update_config -f}} aclocal --force libtoolize --force autoconf --force autoheader --force automake -afc CFLAGS="$RPM_OPT_FLAGS -Wall -Wno-unused" \ ./configure \ --prefix=%{_prefix} \ --libdir=%{_libdir} \ --bindir=%{_bindir} \ --includedir=%{_includedir} \ --sysconfdir=%{_sysconfdir} \ --mandir=%{_mandir} -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Dnia środa, 9 stycznia 2013 00:10:39 doiggl@velocitynet.com.au pisze:
Hello
Question: How can I remove the %suse_update_config part without breaking the entire %build section, What should the new line(s) look like.
The old %build section of the .spec reads as
%build %{?suse_update_config:%{suse_update_config -f}} aclocal --force libtoolize --force autoconf --force autoheader --force automake -afc
AFAIK, all this stuff should be handled by { autoreconf -fi; } HTH, Chris -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Tue, 08 Jan 2013 19:07:19 +0100, Krzysztof Żelechowski <giecrilj@stegny.2a.pl> wrote:
Dnia środa, 9 stycznia 2013 00:10:39 doiggl@velocitynet.com.au pisze:
Hello
Question: How can I remove the %suse_update_config part without breaking the entire %build section, What should the new line(s) look like.
The old %build section of the .spec reads as
%build %{?suse_update_config:%{suse_update_config -f}} aclocal --force libtoolize --force autoconf --force autoheader --force automake -afc
AFAIK, all this stuff should be handled by { autoreconf -fi; }
HTH, Chris Hello Will this %build syntax work ?. I commented out the entie line "#%{?suse_update_config:%{suse_update_config -f}}" And added in the 6 linesbelow it ? %build now reads as [1]
Sourced from # http://en.opensuse.org/openSUSE:Build_Service_cross_distribution_howto #see section "Building on Older Distros" Thanks Glenn [1] %build #%{?suse_update_config:%{suse_update_config -f}} %if 0%{?suse_version} > 1010 autoreconf -fi %else autoheader autoconf %endif CFLAGS="$RPM_OPT_FLAGS -Wall -Wno-unused" \ ./configure \ --prefix=%{_prefix} \ --libdir=%{_libdir} \ --bindir=%{_bindir} \ --includedir=%{_includedir} \ --sysconfdir=%{_sysconfdir} \ --mandir=%{_mandir} make %{?jobs:-j%jobs} CFLAGS="$RPM_OPT_FLAGS -Wall -Wno-unused" -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Dnia sobota, 19 stycznia 2013 21:52:02 doiggl@velocitynet.com.au pisze:
On Tue, 08 Jan 2013 19:07:19 +0100, Krzysztof Żelechowski
<giecrilj@stegny.2a.pl> wrote:
Dnia środa, 9 stycznia 2013 00:10:39 doiggl@velocitynet.com.au pisze:
Hello
Question: How can I remove the %suse_update_config part without
breaking
the entire %build section, What should the new line(s) look like.
The old %build section of the .spec reads as
%build %{?suse_update_config:%{suse_update_config -f}} aclocal --force libtoolize --force autoconf --force autoheader --force automake -afc
AFAIK, all this stuff should be handled by { autoreconf -fi; }
HTH, Chris
Hello Will this %build syntax work ?. I commented out the entie line "#%{?suse_update_config:%{suse_update_config -f}}" And added in the 6 linesbelow it ? %build now reads as [1]
Sourced from # http://en.opensuse.org/openSUSE:Build_Service_cross_distribution_howto #see section "Building on Older Distros"
Thanks Glenn
[1]
%build
#%{?suse_update_config:%{suse_update_config -f}}
Do not comment out lines containing macro invocations. These constructs can only be disabled using %if.
%if 0%{?suse_version} > 1010 autoreconf -fi %else autoheader autoconf %endif
I would rather say autoreconf anyway and tell OBS to use a recent version of autotools instead of the distro version.
CFLAGS="$RPM_OPT_FLAGS -Wall -Wno-unused" \ ./configure \ --prefix=%{_prefix} \ --libdir=%{_libdir} \ --bindir=%{_bindir} \ --includedir=%{_includedir} \ --sysconfdir=%{_sysconfdir} \ --mandir=%{_mandir}
You have %configure for that.
make %{?jobs:-j%jobs} CFLAGS="$RPM_OPT_FLAGS -Wall -Wno-unused"
All in all, the syntax per se has nothing that would inhibit the work of the script, so perhaps it will probably work. Chris -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
<doiggl@velocitynet.com.au> writes:
CFLAGS="$RPM_OPT_FLAGS -Wall -Wno-unused" \ ./configure \
It is preferred to put variable assignments on the command line instead of in the environment.
make %{?jobs:-j%jobs} CFLAGS="$RPM_OPT_FLAGS -Wall -Wno-unused"
You shouldn't have to repeat the setting here. Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
participants (6)
-
Adrian Schröter -
Andreas Jaeger -
Andreas Schwab -
doiggl＠velocitynet.com.au -
Krzysztof Żelechowski -
Marcus Meissner