I am hoping someone, or a few more knowledgeable programmers, can provide an 
answer. 


Problem Statement


I have two packages that successfully build and install, scbuild and scinstall, 
respectively.

The files listed in the .spec file were found, copied, and stored in the 
correct directories in the tmp folder.  Files were confirmed.


However, after executing scdeploy [./ltib -m scdeploy -p <pkg>], the <pkg>.rpm 
has a file size of 1.3KB and is empty, far less than the 12MB.


What is the possible reason(s) this could occur?


Details:


File Specification Type A:


The 20 packages that successfully generate a RPM package containing files have 
a general file list, i.e.

%files

%defattr (-,root,root)

%(pfx)/*


The two packages that generate empty RPM packages were modified to list the 
individual files as a “best coding practice” and provide traceability.


File Specification Type B: 


%files

%defattr (-,root,root)

%{pfx}%{libdir}/libgstaudio-%{majorminor}.so

….





To summarize, File Type A generates a proper RPM package, while Type B 
generates RPM packages that are empty (file size = 1.3KB).


Other Details


TI vendor BSP

Cross-compilation to ARM processor

Modifying spec files to add support for additional Gstreamer plugins

Disto: Ubuntu 14.04.01

LTIB version 1.93



Thank you,


Leo


Sent from Windows Mail
_______________________________________________
LTIB home page: http://ltib.org

Ltib mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/ltib

Reply via email to