Sorry for polluting the whole list, but as I don't have a mentor...

This is the first time I'm building 64-bit packages, and I'm running into the 
following issue.

Requirements such as:

BuildRequires:    qt4-devel 
BuildRequires:    python-devel

expand very well (automatically) on 64-bit into:

lib64qt4-devel 

lib64python-devel

However, requirements such as:

BuildRequires:    magick-devel
BuildRequires:    chm-devel
BuildRequires:    wmf-devel

do NOT expand into the existing:

lib64magick-devel
lib64chm-devel
lib64wmf-devel

therefore I have to use:


BuildRequires:    %{_lib}magick-devel
BuildRequires:    %{_lib}chm-devel
BuildRequires:    %{_lib}wmf-devel

Of course(?), magick-devel%{?_isa} etc. does NOT help.

Question 1: why some libraries name do expand on 64-bit, whereas others don't?

Question 2: why some other libraries expand even when incorrect names are given?
E.g.:
BuildRequires:    libpoppler-qt4-devel

accepts the installed lib:

lib64poppler-qt4-devel

although the name is incorrect, it should be limited to 32-bit!

Is the building system broken, am I stupid, or both?

Thanks, 

R-C aka beranger

Reply via email to