« Return to Thread: Reimplement lapack
Re: Reimplement lapack
by Jessica Jones
::
Rate this Message:
On 04/09/09 23:44, Sascha Manns wrote:
> Am Samstag 05 September 2009 00:28:07 wrote Clint Whaley:
>> Guys,
>>
>>> Can we reimplement in configure --with-netlib
>>> lapack=%{buildroot}%{_libdir}/liblapack_pic.a?
>> All things are possible. I was trying to simplify my life by eliminating
>> it, however. In particular, people tend to build lapack with incompatible
>> flags, and then write in for help because ATLAS doesn't work. I therefore
>> thought I'd simplify the framework by not having this option anymore, and
>> also cut down the user help requests by always having ATLAS build it.
> Maybe we can give both options. So everyone can choose, what he wants.
> The Problem is, we have an own lapack Package in out Buildservice. I add all
> relevant Packages to my chroot (buildroot). Then i can give configure the Path
> to the needed Lib.
> In the present status i must add an Tarfile from an Program, who exists
> already an own Package.
> Do you know what i mean?
>
I assume you are building it as an RPM then? We also do this, but I've
been cheating by getting ATLAS to build it for me, then stealing the
build flags suggested by ATLAS to create the LAPACK RPM, which we keep
separate from one tuned for GotoBLAS by hand using the tools provided
helpfully by ATLAS (yes this is a bit confusing, but it works very well).
Jess
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Math-atlas-devel mailing list
Math-atlas-devel@...
https://lists.sourceforge.net/lists/listinfo/math-atlas-devel
> Am Samstag 05 September 2009 00:28:07 wrote Clint Whaley:
>> Guys,
>>
>>> Can we reimplement in configure --with-netlib
>>> lapack=%{buildroot}%{_libdir}/liblapack_pic.a?
>> All things are possible. I was trying to simplify my life by eliminating
>> it, however. In particular, people tend to build lapack with incompatible
>> flags, and then write in for help because ATLAS doesn't work. I therefore
>> thought I'd simplify the framework by not having this option anymore, and
>> also cut down the user help requests by always having ATLAS build it.
> Maybe we can give both options. So everyone can choose, what he wants.
> The Problem is, we have an own lapack Package in out Buildservice. I add all
> relevant Packages to my chroot (buildroot). Then i can give configure the Path
> to the needed Lib.
> In the present status i must add an Tarfile from an Program, who exists
> already an own Package.
> Do you know what i mean?
>
I assume you are building it as an RPM then? We also do this, but I've
been cheating by getting ATLAS to build it for me, then stealing the
build flags suggested by ATLAS to create the LAPACK RPM, which we keep
separate from one tuned for GotoBLAS by hand using the tools provided
helpfully by ATLAS (yes this is a bit confusing, but it works very well).
Jess
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Math-atlas-devel mailing list
Math-atlas-devel@...
https://lists.sourceforge.net/lists/listinfo/math-atlas-devel
« Return to Thread: Reimplement lapack
| Free embeddable forum powered by Nabble | Forum Help |
