zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Cc: jarausch@igpm.rwth-aachen.de
Subject: Re: zftp.c doesn't compile on IRIX6.5
Date: Sun, 28 May 2000 21:05:55 +0000	[thread overview]
Message-ID: <1000528210555.ZM28309@candle.brasslantern.com> (raw)
In-Reply-To: <E12wA0m-000319-00.2000-05-28-21-50-16@cmailg2.svr.pol.co.uk>

On May 28,  9:50pm, Peter Stephenson wrote:
} Subject: Re: zftp.c doesn't compile on IRIX6.5
}
} There's something extremely screwy here.  If <netinet/in_systm.h> exists,
} why does configure not detect it?  I looked, and whether for the same
} reason or not the test fails on linux, where gcc is outputting a warning
} message:
} 
} In file included from /usr/include/sys/cdefs.h:24,
}                  from /usr/include/netinet/in_systm.h:23,
}                  from configure:2634:
} /usr/include/features.h:254: warning: `__USE_LARGEFILE' redefined
} /usr/include/features.h:198: warning: this is the location of the previous definition
} 
} which is enough to make the test fail.

This is probably the same autoconf/glibc2 thing that's described in the
Etc/MACHINES file for the RLIM_INFINITY macro.

Helmut, were you compiling with GCC also?  If so, did you try with the native
Irix compiler?

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com

Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net   


  reply	other threads:[~2000-05-28 21:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-28 15:53 jarausch
2000-05-28 15:57 ` Geoff Wing
2000-05-28 17:25   ` jarausch
2000-05-28 20:50 ` Peter Stephenson
2000-05-28 21:05   ` Bart Schaefer [this message]
2000-05-29  7:35     ` jarausch
2000-05-29  7:42   ` jarausch

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=1000528210555.ZM28309@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=jarausch@igpm.rwth-aachen.de \
    --cc=zsh-workers@sunsite.auc.dk \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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).