From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeffrey A Law To: Craig Burley Cc: root@scitech.co.uk, egcs@cygnus.com Subject: Re: Notice of compiling egcs-1.0.1 Date: Tue, 05 May 1998 23:29:00 -0000 Message-id: <13212.894434233@hurl.cygnus.com> References: <199805051631.MAA09898@melange.gnu.org> X-SW-Source: 1998-05/msg00168.html In message < 199805051631.MAA09898@melange.gnu.org >you write: > Whoah, that's incredible, another example of "if you know something > that a user does to operate your product won't work at some point, > try to make you product fail in that case as soon, and clearly, > as possible". Yup. Nailing this down took quite a bit of work on Jim's part several months ago. Believe me, it had lots of people stumped. > For my own part, I have *no* idea what "explicit .'s in my environment > variables" means, as I, a Linux user (Intel and Alpha), also get my > egcs copies via ftp. setenv LIBRARY_PATH x:. Gets you an explicit one after "x" :-) setenv LIBRARY_PATH :x: Gets you two implicit ones (one before "x", one after "x"). > Could someone who understands this issue please implement some > early "trap" in the build process (and, if the problem can make > configuring misbehave, early on there as well) so more users > don't run into this problem? It's a "make" time issue, not a configure time issue. As often as it's come up I don't believe trying to work around users with losing environments in the makefiles is the right way to approach the problem. Unfortunately, we can't force folks to read the FAQ (which is available both on the web *and* in the distributions).... jeff