git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Boyd Lynn Gerber <gerberb@zenez.com>
To: Mike Ralphson <mike.ralphson@gmail.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: Bug/problem with 1.6.0 on UnixWare
Date: Thu, 21 Aug 2008 06:18:02 -0600	[thread overview]
Message-ID: <alpine.LNX.1.10.0808210610440.29396@xenau.zenez.com> (raw)
In-Reply-To: <e2b179460808210435w31b911a5ie6059b5628db8138@mail.gmail.com>

On Thu, 21 Aug 2008, Mike Ralphson wrote:
> 2008/8/21 Boyd Lynn Gerber <gerberb@zenez.com>:
> > I am having the same problem on UnixWare as I have with the SCO OpenServer
> > 6. trying to build git-1.6.0.
> >
> > Here is the error.
> >
> >    CC shell.o
> >    AR compat/lib.a
> >    LINK git-shell
> > Undefined                       first referenced
> > symbol                              in file
> > hexval_table                        abspath.o
> > null_sha1                           abspath.o
> > trust_executable_bit                abspath.o
> > has_symlinks                        abspath.o
> > UX:ld: ERROR: Symbol referencing errors. No output written to git-shell
> > gmake: *** [git-shell] Error 1
> 
> I think you've hit the problem described here:
> http://article.gmane.org/gmane.comp.version-control.git/92945/match=git+shell
> 
> Junio's revert of the offending commit is I think in the 'next' branch.

Yep, that sounds about right.  It has bitten me on the 12 platforms, I 
submitted to get git working on them.  I will look at reverting it.  

I just tried to get this working and now I am being flooded with emails 
from people that are trying git for the first time, and asking...

How I could your recommend such a broken SCM?  I told them to got back to 
the 1.5.X but being new to git and then not being able to build and use it 
is causing a lot of flack.  I am getting emails now about my recommending 
git, as it is broken.  I should not have announce to the various lists 
about how great git is and that they should dump their older SCM's in 
favor of git.  Really bad timing on my part.  I just hope these people 
will give git an other try.

Thanks,

--
Boyd Gerber <gerberb@zenez.com>
ZENEZ	1042 East Fort Union #135, Midvale Utah  84047

  reply	other threads:[~2008-08-21 12:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-21 11:25 Bug/problem with 1.6.0 on UnixWare Boyd Lynn Gerber
2008-08-21 11:35 ` Mike Ralphson
2008-08-21 12:18   ` Boyd Lynn Gerber [this message]
2008-08-21 12:41     ` Mike Ralphson
2008-08-21 13:08       ` Jeff King
2008-08-21 14:38         ` Mike Ralphson
2008-08-21 20:45           ` Jeff King
2008-08-22  7:58             ` Mike Ralphson

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=alpine.LNX.1.10.0808210610440.29396@xenau.zenez.com \
    --to=gerberb@zenez.com \
    --cc=git@vger.kernel.org \
    --cc=mike.ralphson@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).