git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H.Merijn Brand" <h.m.brand@xs4all.nl>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org,
	Richard Lloyd <richard.lloyd@connectinternetsolutions.com>
Subject: Re: FYI: Reply from HP-UX
Date: Thu, 17 Jan 2008 19:21:54 +0100	[thread overview]
Message-ID: <20080117192154.5634c62d@pc09.procura.nl> (raw)
In-Reply-To: <alpine.LSU.1.00.0801171811480.5731@racer.site>

On Thu, 17 Jan 2008 18:14:00 +0000 (GMT), Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:

> Hi,
> 
> On Thu, 17 Jan 2008, H.Merijn Brand wrote:
> 
> > On Thu, 17 Jan 2008 16:58:36 +0000 (GMT), Johannes Schindelin
> > <Johannes.Schindelin@gmx.de> wrote:
> > 
> > > On Thu, 17 Jan 2008, H.Merijn Brand wrote:
> > > 
> > > > * Have to force use of /usr/local/bin/perl, otherwise it picks up 
> > > > /usr/bin/perl which the build system doesn't like.
> > > 
> > > This should be handled in your patch to Makefile IMHO.
> > 
> > You mean this: ?
> > --8<---
> > --- Makefile.orig       2007-12-17 07:03:21 +0100
> > +++ Makefile    2007-12-17 18:04:37 +0100
> > @@ -401,6 +401,19 @@ EXTLIBS =
> >  # because maintaining the nesting to match is a pain.  If
> >  # we had "elif" things would have been much nicer...
> > 
> > +ifeq ($(uname_S),HP-UX)
> > +       # HP-UX
> > +       BASIC_LDFLAGS  += -L/usr/local/ssl/lib -L/usr/local/lib
> > +#      EXTLIBS        += -lc_r -lgcc
> > +       NO_HSTRERROR    = YesPlease
> > +       NO_ICONV        = YesPlease
> > +       NO_INET_NTOP    = YesPlease
> > +       NO_INET_PTON    = YesPlease
> > +       NO_UNSETENV     = YesPlease
> > +       NO_STRTOULL     = YesPlease
> > +       NO_STRTOUMAX    = YesPlease
> > +       NO_PREAD        = YesPlease
> > +endif
> 
> Almost:
> 
> +	PERL_PATH = /usr/local/bin/perl

Yep, should work

> > -->8---
> > 
> > Note that this was on HP-UX 11.00/32. A 64bit env on 11.23/64 IPF will be
> > different.
> > 
> > I had no problem with my perl, as I specifically told that on the configure
> > line:
> > 
> > $ ./configure --prefix=/pro/local --disable-nls --without-iconv --with-perl=/pro/bin/perl
> 
> I guess that my suggestion doesn't work... Your perl is not in 
> /usr/local/bin...

This was *my* CONF, not Richard's!

-- 
H.Merijn Brand         Amsterdam Perl Mongers (http://amsterdam.pm.org/)
using & porting perl 5.6.2, 5.8.x, 5.10.x  on HP-UX 10.20, 11.00, 11.11,
& 11.23, SuSE 10.1 & 10.2, AIX 5.2, and Cygwin.       http://qa.perl.org
http://mirrors.develooper.com/hpux/            http://www.test-smoke.org
                        http://www.goldmark.org/jeff/stupid-disclaimers/

  reply	other threads:[~2008-01-17 18:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-17 13:11 FYI: Reply from HP-UX H.Merijn Brand
2008-01-17 16:58 ` Johannes Schindelin
2008-01-17 17:55   ` H.Merijn Brand
2008-01-17 18:14     ` Johannes Schindelin
2008-01-17 18:21       ` H.Merijn Brand [this message]
2008-01-17 18:24         ` Johannes Schindelin
2008-01-17 18:29           ` H.Merijn Brand
2008-01-17 21:17 ` Daniel Barkalow
2008-01-18  1:03 ` [PATCH] autoconf: Add checking for unsetenv function Jakub Narebski

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=20080117192154.5634c62d@pc09.procura.nl \
    --to=h.m.brand@xs4all.nl \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=richard.lloyd@connectinternetsolutions.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).