Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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: <000d01c30f9e$7505a720$5f6886d9@ellixia> From: "Elfyn McBratney" To: "cygwin" , "Joshua Kwan" References: <20030501042813 DOT GA15911 AT triplehelix DOT org> Subject: Re: basename() implementation? Date: Thu, 1 May 2003 05:59:32 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 > I've read the archive and apparently there is a basename function > floating around *somewhere* in cygwin. But what header should I use and > what header should I link against to use it? > > BTW, I'm using libtool now so *supposedly* building shlibs are fixed. Josh, thank you for reminding me to get off my...! {base,dir}name() are not yet implemented, however they should be in the next release > Also, I would like to know why the libtool.m4 for cygwin fancies looking > for a fortran compiler in configure! It's totally nonsensical to me, can > anyone clear this up or tell me how to get rid of it? There is *no* > fortran code in my project. > > Regards, > Josh It shouldn't matter, anyhow IIRC there's an autoconf macro to disable looking for the (a) fortan compiler. Elfyn -- 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/