From: "Jan Djärv" <jan.h.d@swipnet.se>
To: Sascha Wilde <wilde@sha-bang.de>
Cc: emacs-devel@gnu.org
Subject: Re: Pathnames with two (or more) slashes in Makefile.c
Date: Tue, 30 Jan 2007 10:14:49 +0100 [thread overview]
Message-ID: <45BF0C89.7020408@swipnet.se> (raw)
In-Reply-To: <m2bqkg3ngv.fsf@kenny.sha-bang.de>
Sascha Wilde skrev:
> Jan Djärv <jan.h.d@swipnet.se> wrote:
>
>> Sascha Wilde skrev:
>>
>>> Sorry, maybe I'm seriously missing something here, but I can't see
>>> such a change by you, neither in CVS nor in the ChangeLog.
>> I changed src/makefile.in, you have to rerun configure.
>
> Ok, now I see your change.
>
> But I'm sorry to say: it doesn't fix anything. Now Makefile.c
> contains:
>
> XFT_LIBS=-L//lib -L/usr/X11R6/lib -lXft -lXrender -lX11 -lXext -lfontconfig -lfreetype -lz
>
> which has exactly the same problem...
Ahh, how stupid of me. A question about your patch:
> --- a/configure.in
> +++ b/configure.in
> @@ -3256,6 +3256,7 @@
> < Makefile.c > junk1.c
> sed -e '1,/start of cpp stuff/d'\
> -e 's,/\*\*/#\(.*\)$,/* \1 */,' \
> + -e 's,\(#.*\)//\+,\1/,g' \
> < Makefile.c > junk.c
> $CPP $undefs -I. -I$srcdir/src $CPPFLAGS junk.c | \
> sed -e 's/^ / /' -e '/^#/d' -e '/^[
Why is there a \+? Should we not change // to / everywhere, i.e.
s,//,/,g
?
Jan D.
next prev parent reply other threads:[~2007-01-30 9:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-27 19:54 Latest configure.in change breaks building Sascha Wilde
2007-01-28 9:48 ` Jan Djärv
2007-01-28 14:28 ` Pathnames with two (or more) slashes in Makefile.c (was: Latest configure.in change breaks building) Sascha Wilde
2007-01-29 8:06 ` Pathnames with two (or more) slashes in Makefile.c Jan Djärv
2007-01-29 20:21 ` Sascha Wilde
2007-01-30 7:08 ` Jan Djärv
2007-01-30 8:53 ` Sascha Wilde
2007-01-30 9:09 ` Sascha Wilde
2007-01-31 9:36 ` Sascha Wilde
2007-01-31 17:42 ` Jan Djärv
2007-01-31 22:33 ` Sascha Wilde
2007-01-30 9:14 ` Jan Djärv [this message]
2007-01-30 9:47 ` Sascha Wilde
2007-01-30 10:26 ` Jan Djärv
2007-01-30 11:04 ` Sascha Wilde
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45BF0C89.7020408@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=emacs-devel@gnu.org \
--cc=wilde@sha-bang.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.