Wed Jun 29 21:50:00 GMT 2005
On Wed, 29 Jun 2005, James R. Phillips wrote:
> --- Christopher Faylor wrote:
> > FWIW, I don't think we want to start a precedent of official cygwin
> > releases installing things in /usr/local.
> The intent of the packaging design is that the official cygwin binary
> release would _not_ install anything in /usr/local. However, with
> installation of the source package, it would be possible to build the
> locally optimized atlas libraries. These would be compiled from source
> and installed by a local administrator. That being the case, the
> preferred location would be /usr/local, per fhs guidelines.
> The binary release, as initially designed, would install link libraries
> in /usr/lib and dlls in /usr/bin. However, locating the dlls in
> /usr/bin is problematic, because they become impossible to override with
> path manipulations for binaries living in /usr/bin. So this part of the
> design needs to be revised. After thinking about it, I don't think use
> of the /opt tree makes that much sense; probably the easiest
> modification is to create a /usr/bin/lapack subdirectory for the
> nonoptimized libraries to live in, and add it to the back of the path in
> an init.d script. This is what I am leaning towards.
Make that /usr/lib/lapack, please -- see how gcc does it.
|\ _,,,---,,_ email@example.com
ZZZzz /,`.-'`' -. ;-;;,_ firstname.lastname@example.org
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D.
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
"The Sun will pass between the Earth and the Moon tonight for a total
Lunar eclipse..." -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT
More information about the Cygwin-apps