On 04/25/2012 12:06 PM, William Cohen wrote:
> On 04/25/2012 02:31 PM, Matthew LeGendre wrote:
>>> -allow use %configure macro in spec file
>>
>> I don't know my way around spec files, so someone else will have to comment on the state of this and what it would entail. Perhaps Ray?
>
> I have tried to use the %configure macro in the configure files because it pretty much sets everything that might be needed. However, when doing that with the current spec files causes things to fail during the build.
>
>>
>>> -use proper /usr/lib64 for machine that support both 32-bit and 64-bit
>>
>> I tried to figure out the right way to do this, and despite spending significant time googling I was unable to figure it out.
> Does anyone know the proper way to test for and determine the lib install target? Preferably from autoconf?
At least for rpm builds, that's part of the magic in using %configure,
which sets all the paths including --libdir=/usr/lib64.
For manual builds, I don't think autoconf usually does anything special.
So you'll get a default libdir of $prefix/lib if you don't say
otherwise, and it's the user's fault if that's wrong.
>>> -allow exclusion of boost files (use externally supplied ones)
>>
>> This is done, though pending more testing.
I believe the external/boost/ was the easy part, but have you also
addressed the "dyn_detail::boost" clone? I spoke a bit with Ray about
this at pdweek, and while he explained the ABI issues in the past, he
thought it might be ok to excise this one too.
Josh
|
![[Computer Systems Lab]](http://www.cs.wisc.edu/pics/csl_logo.gif){kind=logo}