Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-ID:	<41354D50.204@x-ray.at>
Date:	Wed, 01 Sep 2004 06:17:20 +0200
From:	Reini Urban <rurban AT x-ray DOT at>
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 5.0; de-AT; rv:1.8a2) Gecko/20040714
MIME-Version:	1.0
To:	"Robb, Sam" <sam DOT robb AT timesys DOT com>, cygwin AT cygwin DOT com
Subject:	efsprogs (was: BUG gcc-mingw 20040810-1 library search path)
References:	<3D848382FB72E249812901444C6BDB1D03E04E64 AT exchange DOT timesys DOT com>
In-Reply-To:	<3D848382FB72E249812901444C6BDB1D03E04E64@exchange.timesys.com>
X-IsSubscribed:	yes

Robb, Sam schrieb:
> Already noted, Max.  I'm aware of the problem, but don't have time to address it
> immediately.  I should be able to get to it soon, though.  If you have any suggestions
> as to where the libuuid from e2fsprogs should go, I'd be glad of the advice... IIRC,
> Reini suggested /usr/lib/e2fsprogs or something similar.

Hmm, linux really has it at /usr/lib/

Maybe you could ask the e2fsprogs-devel maintainer to rename his uuid 
lib, or put it into some subdir. "ss" for subsystem seems also to be a 
common name. His headers for example go into subdirs: uuid/uuid.h

It's not the best attitude to trample on these namespaces,
with _libdir=/usr/lib:

%{_libdir}/libcom_err.a
%{_libdir}/libcom_err.so
%{_libdir}/libe2p.a
%{_libdir}/libe2p.so
%{_libdir}/libext2fs.a
%{_libdir}/libext2fs.so
%{_libdir}/libss.a
%{_libdir}/libss.so
%{_libdir}/libblkid.a
%{_libdir}/libblkid.so
%{_libdir}/libuuid.a
%{_libdir}/libuuid.so

-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -