I was trying to build an rpm using the krpmbuilder and ran across a rather cryptic error message. Was hoping someone could point me in the correct direction.
+ CFLAGS=-O2 -g -march=i486 -mcpu=i686
+ CXXFLAGS=-O2 -g -march=i486 -mcpu=i686
+ ./configure --prefix=/opt/kde3
/var/tmp/rpm-tmp.3214: line 27: ./configure: No such file or directory
error: Bad exit status from /var/tmp/rpm-tmp.3214 (%build)
I didn't really change anything in the the %build or %install section. I just went thru the wizard thingy which generates the entire spec file. Left the prefix and configure options as per default as well since I wasn't too sure what those were for.
Many thanks for the help.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This does not seem to be a problem with the current version of krpkbuilder. Krpmbuilder uses the sequence: configure, make, install to build the package. If there is no configure script included in the package you are tyring to build, krpmbuild will fail.
Perhaps you could extract the files of the tar-archive you are trying to build and try to construct the configure script. Maybe there is some autogen.sh script, or something else. Afterwards you create the tarfile out of these files and have another try with krpmbuilder.
I am busy thinking on how to get more options into krpmbuilder, but that' s not an easy task, since there is a lot of ways to build rpm-packages.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for the replies Wolfgang. My experiences with linux is still a little limited I'm afraid so I appologize if this question is a newbie one. Untarring the thing is not an issue since I wrote the entire application. From what I understand I'll now need to add a configure script in the root of my application before i tar gzip it. What I need to find out tho is exactly what's required of me in the construction of the configure script. What is the configure script supposed to do ?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Did some googling and found out what configure files were supposed to do and I think I should clarify. The sources that I'm trying to rpm are already made and are binary distribution builds. For all intents and purposes, you can simply untar/unzip and run from there. For the purpose of conformance to certain distribution requirements tho, I'm having to create an rpm from my distribution builds. As such, I really have no need for a configuration file. There are no makes to be executed and as such no make files to be generated as the source are already binary. In my case, what would you recommend ?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well that's kind of a problem, Michael. Krpmbuilder does not support building a package from the already compiled sources. The build-process for a rpm-package consists of several sections within the spec file:
%prep prepare for the build process (uncompress/tar)
%build build the package
%install do a temporary install
Each section holds the commands to complete the step. You may skip prep or build if you supply parameters to rpm. It is possible not to use the configure/make sequence and using other commands. These commands have to be written into the spec file, which rpm interprets in building the package.
Krpmbuilder has a predefined .spec file (standard.spec) which is modified with your input and then written into the appropriate directory. Just take your favourite texteditor and change the build section to the commands needed to build your application and start rpm from shell. Perhaps you should do a 'man rpm' to get more information on the build process. Maybe you could build a binary package using option -bi when starting rpm or -bb to build a binary package. All this requires that you completed the whole sequence: prep-build-install, since rpm expects the files to be in the right directories.
I am currently work on the home-page for krpmbuilder, but your questions give me some ideas what to implent in further versions of krpmbuilder.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I was trying to build an rpm using the krpmbuilder and ran across a rather cryptic error message. Was hoping someone could point me in the correct direction.
+ CFLAGS=-O2 -g -march=i486 -mcpu=i686
+ CXXFLAGS=-O2 -g -march=i486 -mcpu=i686
+ ./configure --prefix=/opt/kde3
/var/tmp/rpm-tmp.3214: line 27: ./configure: No such file or directory
error: Bad exit status from /var/tmp/rpm-tmp.3214 (%build)
I didn't really change anything in the the %build or %install section. I just went thru the wizard thingy which generates the entire spec file. Left the prefix and configure options as per default as well since I wasn't too sure what those were for.
Many thanks for the help.
This does not seem to be a problem with the current version of krpkbuilder. Krpmbuilder uses the sequence: configure, make, install to build the package. If there is no configure script included in the package you are tyring to build, krpmbuild will fail.
Perhaps you could extract the files of the tar-archive you are trying to build and try to construct the configure script. Maybe there is some autogen.sh script, or something else. Afterwards you create the tarfile out of these files and have another try with krpmbuilder.
I am busy thinking on how to get more options into krpmbuilder, but that' s not an easy task, since there is a lot of ways to build rpm-packages.
Thanks for the replies Wolfgang. My experiences with linux is still a little limited I'm afraid so I appologize if this question is a newbie one. Untarring the thing is not an issue since I wrote the entire application. From what I understand I'll now need to add a configure script in the root of my application before i tar gzip it. What I need to find out tho is exactly what's required of me in the construction of the configure script. What is the configure script supposed to do ?
Did some googling and found out what configure files were supposed to do and I think I should clarify. The sources that I'm trying to rpm are already made and are binary distribution builds. For all intents and purposes, you can simply untar/unzip and run from there. For the purpose of conformance to certain distribution requirements tho, I'm having to create an rpm from my distribution builds. As such, I really have no need for a configuration file. There are no makes to be executed and as such no make files to be generated as the source are already binary. In my case, what would you recommend ?
Well that's kind of a problem, Michael. Krpmbuilder does not support building a package from the already compiled sources. The build-process for a rpm-package consists of several sections within the spec file:
%prep prepare for the build process (uncompress/tar)
%build build the package
%install do a temporary install
Each section holds the commands to complete the step. You may skip prep or build if you supply parameters to rpm. It is possible not to use the configure/make sequence and using other commands. These commands have to be written into the spec file, which rpm interprets in building the package.
Krpmbuilder has a predefined .spec file (standard.spec) which is modified with your input and then written into the appropriate directory. Just take your favourite texteditor and change the build section to the commands needed to build your application and start rpm from shell. Perhaps you should do a 'man rpm' to get more information on the build process. Maybe you could build a binary package using option -bi when starting rpm or -bb to build a binary package. All this requires that you completed the whole sequence: prep-build-install, since rpm expects the files to be in the right directories.
I am currently work on the home-page for krpmbuilder, but your questions give me some ideas what to implent in further versions of krpmbuilder.