From: Louis.Granboulan@ens.fr (Louis Granboulan)
To: zsh-workers@math.gatech.edu
Subject: zsh-3.0-pre5 on Alliant Concentrix 2800
Date: Fri, 2 Aug 1996 14:53:38 +0200 (MET DST) [thread overview]
Message-ID: <199608021253.OAA13246@agaric.ens.fr> (raw)
I built zsh-3.0-pre5 on an architecture not listed in Etc/MACHINES.
The machine is an Alliant Concentrix 2800 3.0.00 known by configure
as i860-alliant-bsd .
I have gcc version 2.1
I did `./configure' and then `make'. It didn't work immediatly.
Here is what I did to make it work.
signals.c:465: `WNOHANG' and `WUNTRACED' undeclared
Diagnostic:
HAVE_SYS_WAIT_H was undefined by ./configure, since sys/wait.h
is not POSIX.1 compatible.
But it is POSIX.1 compatible when _POSIX_SOURCE is defined.
Solution:
This patch:
*** configure.orig Sat Jul 20 19:07:14 1996
--- configure Fri Aug 2 14:43:19 1996
***************
*** 1672,1673 ****
--- 1672,1674 ----
#include "confdefs.h"
+ #define _POSIX_SOURCE
#include <sys/types.h>
*** Src/system.h.orig Mon Jul 1 20:20:44 1996
--- Src/system.h Fri Aug 2 14:50:08 1996
***************
*** 180,182 ****
--- 180,184 ----
#ifdef HAVE_SYS_WAIT_H
+ # define _POSIX_SOURCE
# include <sys/wait.h>
+ # undef _POSIX_SOURCE
#else
Diagnostic:
waitpid does not work
Solution:
#undef HAVE_WAITPID /* in config.h */
zle_main.c:109: `ONLCR' undeclared
Diagnostic:
Not defined in sys/termios.h (probably POSIX compliance)
Solution:
#define ONLCR 0x00000004 /* in zle_main.c */
ld: undefined symbols: __strlen __strcpy __strncpy
Diagnostic:
Might be a bug in the libc of gcc
Solution:
Compiling and linking this file : strings.c
int _strlen(s) char *s;
{return strlen(s);}
char *_strcpy(s1,s2) char *s1,*s2;
{return strcpy(s1,s2); }
char *_strncpy(s1,s2,n) char *s1,*s2; int n;
{return strncpy(s1,s2,n);}
reply other threads:[~1996-08-02 13:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=199608021253.OAA13246@agaric.ens.fr \
--to=louis.granboulan@ens.fr \
--cc=zsh-workers@math.gatech.edu \
/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).