Date: Thu, 22 Aug 2002 23:12:57 +0400 (MSD) From: Dmitry Morozovsky <marck@rinet.ru> To: Skye Poier <skye@ffwd.cx> Cc: stable@FreeBSD.ORG Subject: Re: ports problems -- FIXED Message-ID: <20020822231154.A49131-100000@woozle.rinet.ru> In-Reply-To: <20020822114419.G43401@ffwd.cx>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 22 Aug 2002, Skye Poier wrote:
SP> This is one of the things that really annoys me about the UNIX
SP> "community". Why do you have to be a assh*le and blame me for a
SP> completely non-intuitive mistake? Its not even a mistake really,
SP> show me a man page or a handbook entry where it says "don't put trailing
SP> slashes in your path".. and since I've been running it this way for
SP> years, and haven't had any problems other than this libtool failure, I'd
SP> say the problem lies in bsd.port.mk, not my .tcshrc
Well, take a deep breath please. Then, try the following patch to
bsd.port.mk:
Index: bsd.port.mk
===================================================================
RCS file: /home/ncvs/ports/Mk/bsd.port.mk,v
retrieving revision 1.422
diff -u -r1.422 bsd.port.mk
--- bsd.port.mk 19 Aug 2002 17:12:59 -0000 1.422
+++ bsd.port.mk 22 Aug 2002 19:11:38 -0000
@@ -2638,7 +2638,7 @@
${ECHO_CMD} "and reinstall ${PORTSDIR}/devel/libtool."; \
exit 1); \
fi; \
- LIBTOOLDIR=`${WHICH} ${LIBTOOL} | ${SED} -e
's^/bin/libtool^/share/libtool^'` || ${LOCALBASE}/share/libtool; \
+ LIBTOOLDIR=`${WHICH} ${LIBTOOL} | ${SED} -e
's^/bin//*libtool^/share/libtool^'` || ${LOCALBASE}/share/libtool; \
cd ${PATCH_WRKSRC}; \
for file in ${LIBTOOLFILES}; do \
${CP} $$file $$file.tmp; \
SP> > > I found my problem.
SP> > >
SP> > > On like 2641 of bsd.port.mk:
SP> > >
SP> > > LIBTOOLDIR=`${WHICH} ${LIBTOOL} | ${SED} -e 's^/bin/libtool^/share/libtool^'` || ${LOCALBASE}/share/libtool; \
SP> > >
SP> > > However, my .tcshrc file contained set path = (... /usr/local/bin/ ...)
SP> > > note the trailing slash.
SP> > >
SP> > > `which libtool` returned /usr/local/bin//libtool
SP> > > which screwed up the sed substitution above.
SP> > >
SP> > > I think this should be fixed??? Probably by eliminating dup // in
SP> > > tcsh's which command?
SP> >
SP> > Eliminating the extra slash in your path variable would be a more
SP> > appropriate fix...
Sincerely,
D.Marck [DM5020, DM268-RIPE, DM3-RIPN]
------------------------------------------------------------------------
*** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru ***
------------------------------------------------------------------------
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020822231154.A49131-100000>