Bugs item #772260, was opened at 2003-07-16 07:28 Message generated for change (Comment added) made by jenos You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=109368&aid=772260&group_id=9368
Category: Packages Group: 2.3 >Status: Closed Resolution: None Priority: 8 Submitted By: Jeff Squyres (jsquyres) Assigned to: Jeremy Enos (jenos) Summary: gm package doesn't build RPM properly Initial Comment: I'm afraid that the xterm downloading the gm tarball disappeared before I could snarf the output. But it looks like it downloaded successfully, and I have a valid packages/gm/src/gm-1.6.4_Linux_and_AIX.tar.gz tarball (i.e., I can tar ztf it without error). There appears to be 2 errors when trying to build the RPM: ----- Preparing... ########################################### [100%] 1:kernel-source ########################################### [100%] Found kernel source from /lib/modules/2.4.18-14/build symlink... Matched current kernel 2.4.18-14. Using kernel source from: /usr/src/linux-2.4.18-14 Using ../src/gm-1.6.4_Linux_and_AIX.tar.gz for gm source file... tar: Error in writing to standard output tar: Error is not recoverable: exiting now Detected OS is redhat Using kernel source /usr/src/linux-2.4.18-14 Current kernel is 2.4.18-14 GM source file is ../src/gm-1.6.4_Linux_and_AIX.tar.gz GM source version is 1.6.4 GM kernel name will be k2.4.18r14 -ba: unknown option real 0m0.076s user 0m0.000s sys 0m0.010s Press any key to exit ----- I don't know what the first error is complaining about (something with tar -- perhaps improper use of $PACKAGE_HOME such that it couldn't find the tarball...?). The second is the "-ba" error. This is a well-known problem that rpm changed the command used to build RPMs at some point (I forget which version offhand). I was attempting to build this on RH 8.0. You might want to use "rpmbuild -ba" instead of "rpm -ba", because (IIRC) this command works just about everywhere (RH 7.x, 8.0, 9.0, MDK, etc.). ---------------------------------------------------------------------- >Comment By: Jeremy Enos (jenos) Date: 2003-07-18 18:44 Message: Logged In: YES user_id=270124 Was the tar error a date/time stamp warning perhaps? The xterm scripts are designed to run through on their own, but stick around if an error was encountered. This problem was just due to rpm vs rpmbuild... easy fix. (fixed) ---------------------------------------------------------------------- Comment By: Jeff Squyres (jsquyres) Date: 2003-07-16 07:37 Message: Logged In: YES user_id=11722 I should add that it looks like the gm tarball and gm_mapper script were successfully copied to /usr/src/redhat/SOURCES, and the spec file was successfully copied to /usr/src/redhat/SPECS. So I'm a little puzzled/worried as to what that tar error was. Unfortunately, the gm_build_rpm.sh script is long and complicated, and I don't have time to look into it. So I leave it up to the package maintainer. :-) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=109368&aid=772260&group_id=9368 ------------------------------------------------------- This SF.net email is sponsored by: VM Ware With VMware you can run multiple operating systems on a single machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the same time. Free trial click here: http://www.vmware.com/wl/offer/345/0 _______________________________________________ Oscar-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/oscar-devel
