From: Paul Jakma <paul@clubi.ie>
To: skimo@liacs.nl
Cc: Peter Eriksen <s022018@student.dtu.dk>,
Junio C Hamano <junkio@cox.net>,
Uwe Zeisberger <zeisberg@informatik.uni-freiburg.de>,
git@vger.kernel.org
Subject: Re: git and Solaris 8
Date: Mon, 18 Sep 2006 15:05:45 +0100 (IST) [thread overview]
Message-ID: <Pine.LNX.4.64.0609181452140.12833@sheen.jakma.org> (raw)
In-Reply-To: <20060918134100.GL1221MdfPADPa@greensroom.kotnet.org>
On Mon, 18 Sep 2006, Sven Verdoolaege wrote:
> All I know is that I have a Solaris *8* machine here and that I
> _don't_ need NEEDS_LIBICONV. There is no -liconv on this machine.
> (I'm CC'ing Uwe, because he apparently also has access to a Solaris
> 8 machine).
I tested on S10, SNV (probably somewhere around SNV_14, can't quite
remember) and S9 (whichever the latest update was). None need
-liconv, it's a build error on S10 (which was the one I cared about).
I can dig into the Iconv situation further later in the week, or
next. I am away from home at moment.
> So is the current setting correct on some versions of Solaris 8 and
> if so, is there some way to change this setting from the command
> line ?
I couldn't find an S8 machine to test on, so I left S8 alone -
existing behaviour, I had no basis to judge it incorrect. S8 is
/really/ old now btw. ;)
> Btw, like Uwe, I also don't have a "gtar" and "ginstall" on this machine.
S10, maybe S9 too (not sure), install these to /usr/sfw/bin, if you
installed everything.
regards,
--
Paul Jakma paul@clubi.ie paul@jakma.org Key ID: 64A2FF6A
Fortune:
Interference from lunar radiation
prev parent reply other threads:[~2006-09-18 14:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-18 13:41 git and Solaris 8 Sven Verdoolaege
2006-09-18 14:05 ` Paul Jakma [this message]
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=Pine.LNX.4.64.0609181452140.12833@sheen.jakma.org \
--to=paul@clubi.ie \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=s022018@student.dtu.dk \
--cc=skimo@liacs.nl \
--cc=zeisberg@informatik.uni-freiburg.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).