Hi Frank:

On 05/05/2015 06:55 PM, Frank Loeffler wrote:
> Hi,
> 
> Doesn't this patch always set BOOST_*_DIRS to some multi-arch
> directory (if gcc is found), even if it was installed in a standard
> location (/usr or /usr/local)? Shouldn't it only set these if a
> multi-arch directory is actually found?
> 
I see your point. I updated the patch with Erik's changes and
add ${BOOST_DIR}/lib. However I don't see the reason to single out
/usr and /usr/local to do nothing with respect to setting BOOST_*_DIRS
as it was before. Do you know the rationale for that?

Thanks,
Bruno.

> Frank
> 
> On Tue, May 05, 2015 at 04:34:27PM +0000, [email protected] wrote:
>> User: bmundim
>> Date: 2015/05/05 11:34 AM
>>
>> Modified:
>>  /trunk/
>>   configure.sh
>>
>> Log:
>>  Define multiarch library directory.
>>  
>>  See discussions at https://trac.einsteintoolkit.org/ticket/1769
>>
>> File Changes:
>>
>> Directory: /trunk/
>> ==================
>>
>> File [modified]: configure.sh
>> Delta lines: +11 -1
>> ===================================================================
>> --- trunk/configure.sh       2014-05-29 20:47:04 UTC (rev 6)
>> +++ trunk/configure.sh       2015-05-05 16:34:26 UTC (rev 7)
>> @@ -151,9 +151,19 @@
>>  # Configure Cactus
>>  
>> ################################################################################
>>  
>> +# Set library directory name for machine architecture:
>> +gcc -dumpversion > /dev/null 2>&1
>> +
>> +if [ $? -eq 0 ]; then
>> +  MACHINE=${MACHINE:=`gcc -dumpmachine`}
>> +else
>> +  MACHINE=${MACHINE:=""}
>> +fi
>> +
>>  # Set options
>>  if [ "${BOOST_DIR}" = '/usr' -o "${BOOST_DIR}" = '/usr/local' ]; then
>> -    :                           # do nothing
>> +    BOOST_INC_DIRS="${BOOST_DIR}/include"
>> +    BOOST_LIB_DIRS="${BOOST_DIR}/lib/${MACHINE}"
>>  else
>>      BOOST_INC_DIRS="${BOOST_DIR}/include"
>>      if [ -d ${BOOST_DIR}/lib64 ]; then
>>
>> _______________________________________________
>> Commits mailing list
>> [email protected]
>> http://cactuscode.org/mailman/listinfo/commits
>>
>>
>> _______________________________________________
>> Users mailing list
>> [email protected]
>> http://cactuscode.org/mailman/listinfo/users

_______________________________________________
Users mailing list
[email protected]
http://cactuscode.org/mailman/listinfo/users

Reply via email to