On Tue, 2008-02-12 at 16:03 +0900, John Summerfield wrote: > Brad Hinson wrote: > > The error is actually coming from mtx, which is a dependency packaged > > with bacula. If you cd into BUILD/depkgs/mtx-1.3.11 and > > run ./configure, you'll see the same error: > > > > --- > > checking build system type... Invalid configuration > > `s390x-unknown-linux-gnu': machine `s390x-unknown' not recognized > > configure: error: /bin/sh ./config.sub s390x-unknown-linux-gnu failed > > --- > > > > The problem is that the machine arch is 's390x', and mtx expects 's390'. > > Attached is a patch to fix this. Here's one way to apply it. The basic > > idea is to untar the tarball containing mtx, apply the patch, then > > re-tar it: > > > > 1.) Save the patch to /tmp/mtx-s390x.patch > > 2.) cd to the .../SOURCES directory > > 3.) cp depkgs-09Sep07.tar.gz depkgs-09Sep07.tar.gz.orig > > 4.) tar xvzf depkgs-09Sep07.tar.gz > > 5.) cd depkgs/mtx-1.3.11/ > > 6.) patch -p0 < /tmp/mtx-s390x.patch > > 7.) cd ../.. > > 8.) tar cvzf depkgs-09Sep07.tar.gz depkgs > > Er > A primary concept with rpm (and dpkg for that matter) is to package the > _unaltered_ _original_ source, and to patch that source at the time of > building. > > Pretty much any source rpm you can find does this, if changes are > required, whether to fix problems (such as this) or to bend the package > to the distro's standards. > > The documentation for first release of RHL I used (3.0.3) goes though > this in some detail, and so did the book "Maximum RPM." I believe the > latter was published to www.rpm.org; unless it's been updated, the > information is fairly old and will need some translation for recent > versions. >
You caught me. I agree, it is much better to patch it correctly. But at ~2500 lines, the bacula spec file is a beast to edit, and I thought that would scare off any newcomers to rpmbuild. :) Attached is a spec file patch. From the SPECS/ dir, run 'patch -p0 < baculaspec.patch'. It's not ideal because there's no easy way to increment the version (it's stored in %release, but if you change that you'd have to rename some files to match). But overall a much cleaner way to do this. Thanks, -Brad > > > > Now, rpmbuild will pick up the new tarball and (should) complete > > successfully. > > > > -Brad > > > > On Mon, 2008-02-11 at 17:36 +0200, Bruce Arro wrote: > >> Hi > >> > >> > >> > >> I trying to do a "rpmbuild -ba bacula.spec" > >> > >> > >> > >> I aways get this message > >> > >> > >> > >> s390-unknown-linux-gnu > >> > >> > >> > >> This is a SLES 10 SP1 enviroment. > >> > >> > >> > >> Any clues? > >> > >> > >> > > > > > -- > > Cheers > John > > -- spambait > [EMAIL PROTECTED] [EMAIL PROTECTED] > -- Advice > http://webfoot.com/advice/email.top.php > http://www.catb.org/~esr/faqs/smart-questions.html > http://support.microsoft.com/kb/555375 > > You cannot reply off-list:-) > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 -- Brad Hinson <[EMAIL PROTECTED]> Sr. Support Engineer Lead, System z Red Hat, Inc. (919) 754-4198 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
--- bacula.spec.orig +++ bacula.spec @@ -34,6 +34,7 @@ Source3: http://www.prdownloads.sourceforge.net/bacula/%{name}-docs-%{docs_version}.tar.gz Source4: http://www.prdownloads.sourceforge.net/bacula/%{name}-rescue-%{_rescuever}.tar.gz Source5: bacula-2.2.7-postgresql.patch +Patch0: mtx-s390x.patch BuildRoot: %{_tmppath}/%{name}-root URL: http://www.bacula.org/ Vendor: The Bacula Team @@ -1196,6 +1197,7 @@ %setup -T -D -b 2 %setup -T -D -b 3 %setup -T -D -b 4 +%patch0 -p1 -b .mtx-s390x %build
