<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'><span style="font-size: 12pt;">> %_prefix /%{MY_BASE}</span><div><br><style><!--
.ExternalClass .ecxhmmessage P {
padding:0px;
}
.ExternalClass body.ecxhmmessage {
font-size:12pt;
font-family:Calibri;
}
--></style></div><div>I should also add that you should pick a top-level directory in opt, like for example "blabla" or some other generic name (usually your organization's name, acronym, or most preferrably, lower case version of your organization's stock symbol, if you have one), and all RPM's you build should end up in the following hierachy, I am using a made-up name "blabla" in the example:</div><div><br></div><div>/opt/blabla/sbin</div><div>/opt/blabla/bin</div><div>/opt/blabla/lib</div><div>/opt/blabla/lib64</div><div>/opt/blabla/libexec</div><div>/etc/opt/blabla/openldap</div><div>/etc/opt/blabla/pdns</div><div>/var/opt/blabla/openldap</div><div>/var/opt/blabla/pdns</div><div><br></div><div>With %MY_BASE (or more appropriately to this example, %BLABLA_BASE) being set to opt/blabla, all SRPM's one (re)builds from that point on should be able to correctly find their files under the /opt/blabla/ hierarchy. This includes libraries.</div> </div></body>
</html>