zsh-workers
 help / color / mirror / code / Atom feed
From: dfavor@corridor.com (The Corridor)
To: zsh-workers@sunsite.auc.dk
Subject: Re: zsh-3.1.6-dev-22 broken several ways on AIX
Date: Tue, 11 Apr 2000 10:57:11 -0600 (MDT)	[thread overview]
Message-ID: <200004111657.KAA20077@corridor.com> (raw)

> On Apr 11, 10:08am, The Corridor wrote:
> } Subject: zsh-3.1.6-dev-22 broken several ways on AIX
> }
> } Several problems show up in this snapshot:
> } 
> } 1) -disable-dynamic no longer works, modules always seem to be enabled.
> 
> You didn't have this problem with -dev-21 ?  There haven't been any
> interesting changes to the build process in a very long time, except
> maybe my patch in 10499, but that shouldn't affect AIX specially.

Best I can tell this occurs in -dev-21 and -dev-22. -dev-20 seemed to work,
as best I can recall.

> Are you using the FTP snapshots, or the SourceForge CVS repository?  If
> the latter, did you remember to run Util/preconfig before making?

FTP'ed snapshot.

> Did you start from scratch or were you compiling in a directory where an
> earlier version had been built before?

Starting from a clean untar into the directory.

> } 2) the GETGPRGP macro should resolve to getpgrp(), not getpgrp(0).
> 
> That configure test hasn't changed in a *very* long time.  When was the
> last snapshot you built successfully?

I know. I've been hand-munging this and the "#pragma alloca" statement
in system.h for quite a while. To support alloca requires the '-ma' option
at compile time. The "#pragma alloca" generates a warning for every source
file compiled.

If it would help I can untar the source in a fresh directory and send you
a log of each step. Maybe that might surface the problem.


             reply	other threads:[~2000-04-11 16:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-11 16:57 The Corridor [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-04-11 16:08 The Corridor
2000-04-11 16:41 ` Bart Schaefer
2000-04-11 17:18 ` Oliver Kiddle
2000-04-11 18:13   ` Bart Schaefer

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=200004111657.KAA20077@corridor.com \
    --to=dfavor@corridor.com \
    --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).