From: Matthieu Moy <Matthieu.Moy@imag.fr>
To: "Giovanni Funchal" <gafunchal@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Patch for NO_R_TO_GCC_LINKER
Date: Wed, 13 Aug 2008 13:32:59 +0200 [thread overview]
Message-ID: <vpqtzdpcfpw.fsf@bauges.imag.fr> (raw)
In-Reply-To: <c475e2e60808130342r452fae1cm7d08d8d2206d0468@mail.gmail.com> (Giovanni Funchal's message of "Wed\, 13 Aug 2008 12\:42\:30 +0200")
"Giovanni Funchal" <gafunchal@gmail.com> writes:
> Hi,
Hi Giovanni, glad to see you here ;-).
> I'm proposing the patch below
Please, read Documentation/SubmittingPatches.
I advise you to use git send-email to send your patches, this one has
(gmail-related) whitespace damage. Read about Signed-Off-By too.
> @@ -226,7 +226,8 @@ INSTALL = install
> RPMBUILD = rpmbuild
> TCL_PATH = tclsh
> TCLTK_PATH = wish
> -
> +LD_RUNPATH_SWITCH = -Wl,-rpath,
> +
Whitespace damage: the - and the + are equal (I suppose you added a
trailing whitespace, which you shouldn't have, and gmail stripped it).
> - CURL_LIBCURL = -L$(CURLDIR)/$(lib) $(CC_LD_DYNPATH)$(CURLDIR)/$(lib) -lcurl
> + CURL_LIBCURL = -L$(CURLDIR)/$(lib)
> $(LD_RUNPATH_SWITCH)$(CURLDIR)/$(lib) -lcurl
Whitespace damage again.
> + AC_MSG_ERROR([no linker support for runtime path to dynamic libraries])
I don't think you should error out here: Git can still be compiled and
can still run without this support (just use $LD_LIBRARY_PATH if
needed). Keeping -R with a big warning would avoid having a regression
in this case.
Thanks,
--
Matthieu
next prev parent reply other threads:[~2008-08-13 11:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-13 10:42 Patch for NO_R_TO_GCC_LINKER Giovanni Funchal
2008-08-13 11:32 ` Matthieu Moy [this message]
2008-08-13 20:10 ` Junio C Hamano
2008-08-13 21:20 ` Giovanni Funchal
2008-08-13 21:50 ` Junio C Hamano
2008-08-13 22:12 ` Junio C Hamano
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=vpqtzdpcfpw.fsf@bauges.imag.fr \
--to=matthieu.moy@imag.fr \
--cc=gafunchal@gmail.com \
--cc=git@vger.kernel.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).