git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: dev <dev@cor0.com>
To: git@vger.kernel.org, "\"René Scharfe\"" <l.s.r@web.de>
Cc: Karsten Blees <karsten.blees@gmail.com>,
	Junio C Hamano <gitster@pobox.com>
Subject: Re: "trace.c", line 219: error: identifier redeclared: trace_strbuf
Date: Sun, 7 Sep 2014 13:19:19 -0400 (EDT)	[thread overview]
Message-ID: <2059998579.17018.1410110359755.JavaMail.vpopmail@webmail2.networksolutionsemail.com> (raw)
In-Reply-To: <540B742F.5030700@web.de>



On September 6, 2014 at 4:53 PM "René Scharfe" <l.s.r@web.de> wrote:
> Am 06.09.2014 um 21:26 schrieb dev:
> >
> >
<snip>
> >
> > Solaris 10 with Oracle Studio 12.3 compiler tools. A lengthy
> > maillist
> > discussion last week sorted out the previous release of git just
> > fine however this release fails to build.
> >
>
> The issue was introduced with e05bed96 (trace: add 'file:line' to all
> trace output).
>
> -- >8 --
> Subject: [PATCH] trace: correct trace_strbuf() parameter type for
> !HAVE_VARIADIC_MACROS
>
> Reported-by: dev <dev@cor0.com>
> Signed-off-by: Rene Scharfe <l.s.r@web.de>
> ---
>  trace.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/trace.c b/trace.c
> index 54aaee5..b6f25a2 100644
> --- a/trace.c
> +++ b/trace.c
> @@ -216,7 +216,7 @@ void trace_argv_printf(const char **argv, const
> char *format, ...)
>    va_end(ap);
>  }
> 
> -void trace_strbuf(const char *key, const struct strbuf *data)
> +void trace_strbuf(struct trace_key *key, const struct strbuf *data)
>  {
>    trace_strbuf_fl(NULL, 0, key, data);
>  }
> --
> 2.1.0
>

Thank you for the reply and the info.  I backed that out and things get
worse :

$ diff -h trace.c.backup trace.c
219,221c219,221
< void trace_strbuf(const char *key, const struct strbuf *data)
< {
<       trace_strbuf_fl(NULL, 0, key, data);
---
> void trace_strbuf(struct trace_key *key, const struct strbuf *data)
> {
>         trace_strbuf_fl(NULL, 0, key, data);


$ gmake CFLAGS="$CFLAGS" LDFLAGS="$LD_OPTIONS" NEEDS_LIBICONV=Yes \
> SHELL_PATH=/usr/local/bin/bash \
> SANE_TOOL_PATH=/usr/local/bin \
> USE_LIBPCRE=1 LIBPCREDIR=/usr/local CURLDIR=/usr/local \
> EXPATDIR=/usr/local NEEDS_LIBINTL_BEFORE_LIBICONV=1 \
> NEEDS_SOCKET=1 NEEDS_RESOLV=1 USE_NSEC=1 \
> PERL_PATH=/usr/local/bin/perl \
> TAR=/usr/bin/tar \
> NO_PYTHON=1 DEFAULT_PAGER=/usr/xpg4/bin/more \
> DEFAULT_EDITOR=/usr/local/bin/vim DEFAULT_HELP_FORMAT=man \
> prefix=/usr/local
    CC trace.o
"trace.c", line 390: error: reference to static identifier "offset" in
extern inline function
"trace.c", line 392: error: reference to static identifier "offset" in
extern inline function
"trace.c", line 393: error: reference to static identifier "offset" in
extern inline function
"trace.c", line 401: error: reference to static identifier "offset" in
extern inline function
"trace.c", line 403: error: reference to static identifier "offset" in
extern inline function
cc: acomp failed for trace.c
gmake: *** [trace.o] Error 2
$

So is there a possible 2.1.1 coming along shortly ?

dev

  reply	other threads:[~2014-09-07 17:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-06 19:26 "trace.c", line 219: error: identifier redeclared: trace_strbuf dev
2014-09-06 20:53 ` René Scharfe
2014-09-07 17:19   ` dev [this message]
2014-09-08 18:11   ` 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=2059998579.17018.1410110359755.JavaMail.vpopmail@webmail2.networksolutionsemail.com \
    --to=dev@cor0.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=karsten.blees@gmail.com \
    --cc=l.s.r@web.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.
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).