Frustration making an RPM package

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I had similar issues with not needing a build and was wondering how this 
really work. Fortunately someone gave me a clue to the structure and I 
was able to get my thing to work. Since it was cool after understanding 
it, I decided to post a web page on how I constructed my rpm with out a 
"%build". Of course my company wants a little promotion so I can use 
their web site, but I think this will answer your question and show you 
how simple it really is to make one without a build. The diagrams are 
the secret. Any comments are welcome.

http://www.logiqwest.com/dataCenter/TechnicalPapers/rpmScriptInstall.html

Hope it helps

Greg_Swift at aotx.uscourts.gov wrote:
>> Hi group,
>>
>> I'm beating my head agains a rock here. I have a package I want to
>> create on a RH9 box using rpmbuild. The package contains an executable,
>> some libs and a coupld of documents, kinda like this...
>>
>> /usr/bin/binary
>> /usr/lib/lib1.so.1.1.1
>> /usr/lib/lib2.so.2.2.2
>> /usr/lib/lib3.so.3.3.3
>> /usr/share/man/man1/binary.1.gz
>> /usr/doc/documents/doc1.txt
>> /usr/doc/documents/doc2.txt
>>
>> I'm not making rpm do the source code build. I'm just supplying the
>> files in a subfolder "package-4.4.4" and letting rpmbuild make the
>> binary package from the resulting .tar.gz file of this collection of
>> files.
>>
>> I started slow and make the first RPM build with only the binary. I then
>> added the man page and documents.
>>
>> The libraries are giving me a problem.
>>
>> rpmbuild -bb -vv gives me the following error:
>>
>> Requires: /sbin/ldconfig libc.so.6 libc.so.6(GLIBC_2.0)
>> libc.so.6(GLIBC_2.1) libc.so.6(GLIBC_2.1.3) libc.so.6(GLIBC_2.3)
>> libdl.so.2 libdl.so.2(GLIBC_2.0) libdl.so.2(GLIBC_2.1) libgcc_s.so.1
>> libgcc_s.so.1(GCC_3.0) libm.so.6 libpthread.so.0
>> libpthread.so.0(GLIBC_2.0) libstdc++.so.5 libstdc++.so.5(CXXABI_1.2)
>> libstdc++.so.5(GLIBCPP_3.2)
>> Checking for unpackaged file(s): /usr/lib/rpm/check-files %{buildroot}
>> D:      execv(/usr/lib/rpm/check-files) pid 25143
>> getOutputFrom(): Broken pipe
>> make: *** [shared-rpm] Error 1
>>     
>
> you really should search google and/or the archives.
>
> Found this in thread of first result for "rpmbuild getOutputFrom":
>
> http://osdir.com/ml/linux.redhat.rpm.general/2002-10/msg00342.html
>
>   
>> Also, the rpmbuild procedure seems to copy the files to their destinaion
>> folders during the build process (e.g. "binary" actually ends up in the
>> /usr/bin folder on the build machine when I run "rpmbuild -vv -bb").
>>
>> Any thoughts on what I'm doing wrong here?
>>     
>
> Try reading through the previous thread entitled "How do I install an
> entire directory under /var with rpm"
>
> good luck.
>
> -greg
>
> _______________________________________________
> Rpm-list mailing list
> Rpm-list at lists.rpm.org
> http://lists.rpm.org/mailman/listinfo/rpm-list
>
>   

-- 
------------------------------------------------------------------------
*Michael Barto*
Software Architect

	LogiQwest Circle
LogiQwest Inc.
16458 Bolsa Chica Street, # 15
Huntington Beach, CA  92649
http://www.logiqwest.com/

	    	mbarto at logiqwest.com <mailto:mbarto at logiqwest.com>
Tel:  714 377 3705
Fax: 714 840 3937
Cell: 714 883 1949

*'tis a gift to be simple*
------------------------------------------------------------------------
This e-mail may contain LogiQwest proprietary information and should be 
treated as confidential.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.rpm.org/pipermail/rpm-list/attachments/20081108/c4bd77a8/attachment.htm 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: circle.gif
Type: image/gif
Size: 651 bytes
Desc: not available
Url : http://lists.rpm.org/pipermail/rpm-list/attachments/20081108/c4bd77a8/attachment.gif 


[Index of Archives]     [RPM Ecosystem]     [Linux Kernel]     [Red Hat Install]     [PAM]     [Red Hat Watch]     [Red Hat Development]     [Red Hat]     [Gimp]     [Yosemite News]     [IETF Discussion]

  Powered by Linux