From: Junio C Hamano <gitster@pobox.com>
To: Robert Schiele <rschiele@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] add definitions for global variables to shell.c
Date: Mon, 18 Aug 2008 17:29:11 -0700 [thread overview]
Message-ID: <7vy72tkfu0.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20080818123727.GB11842@schiele.dyndns.org> (Robert Schiele's message of "Mon, 18 Aug 2008 14:37:27 +0200")
Robert Schiele <rschiele@gmail.com> writes:
> Commit 5b8e6f85 introduced stubs for three functions that make no sense
> for git-shell. But those stubs defined libgit.a functions a second time
> so that a linker can complain. While commit 78568448 fixes this problem
> it introduces a new issue on the affected systems: Some versions of the
> Sun compiler generate references to global variables when they see
> extern declarations for those, even when they are never used in the
> code.
Haven't looked at the real declarations but if the decl are "extern" and
nobody refers to them, why should the resulting object file require them
to be defined anywhere? If the decl are not and in (fortran-ish) "common"
section, on the other hand, you shouldn't have to define them yourself
like this either.
This sounds like a compiler bug to me.
next prev parent reply other threads:[~2008-08-19 0:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-18 12:37 [PATCH] add definitions for global variables to shell.c Robert Schiele
2008-08-19 0:29 ` Junio C Hamano [this message]
2008-08-19 7:26 ` Robert Schiele
2008-08-19 7:53 ` Junio C Hamano
2008-08-19 8:16 ` Robert Schiele
2008-08-19 8:49 ` Johannes Sixt
2008-08-19 9:18 ` Robert Schiele
2008-08-19 23:09 ` Junio C Hamano
2008-08-20 1:06 ` [PATCH 1/2] shell: do not play duplicated definition games to shrink the executable Junio C Hamano
2008-08-20 1:06 ` [PATCH 2/2] Build-in "git-shell" Junio C Hamano
2008-08-20 6:54 ` Johannes Sixt
2008-08-20 1:06 ` [PATCH] add definitions for global variables to shell.c Junio C Hamano
2008-08-20 4:36 ` Robert Schiele
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=7vy72tkfu0.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=rschiele@gmail.com \
/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).