zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.dk (Zsh hackers list)
Cc: Jason Price <jprice@CyberBuzz.GaTech.edu>
Subject: Re: Bugs on SourceForge
Date: Mon, 14 May 2001 16:21:44 +0000	[thread overview]
Message-ID: <1010514162145.ZM10006@candle.brasslantern.com> (raw)
In-Reply-To: <Tc0a88d0153848921ba@mailsweeper01.cambridgesiliconradio.com>

On May 14,  4:23pm, Peter Stephenson wrote:
}
} I'll have to try this out when I get a moment.  But given the headers are
} screwy for Solaris 8 (see below), I rather suspect I won't be able to
} reproduce it.  Certainly works OK on 8 with zsh compiled under 6.

Note that it was Solaris 6 where Jason is having `rlimit64' problems, so
the fact that you're able to compile on Solaris 6 but he is not may be
indicative of ... something ...

} > On to the datasize tests.
} 
} These worked, right?  Else I'm missing something.

They worked.  I closed out the bug report on SourceForge.
 
} > In file included from /usr/include/sys/wait.h:24, from configure:2638:
} > /usr/include/sys/resource.h:148: warning: `struct rlimit64' declared inside 
} > 					  parameter list
} 
} This looks like another header problem, but this time it's more than just
} configure complaining.  struct rlimit64 should be defined:
[...]
} 5.8 system.  The complaints are presumbably from the lines
} 
}   extern int setrlimit64(int, const struct rlimit64 *);
}   extern int getrlimit64(int, struct rlimit64 *);

Your header certainly makes it appear that it shouldn't be possible to
compile the above two lines without also having rlimit64 defined.  I've
already sent mail to Jason asking what his resource.h looks like (and
he's Cc'd on this message).

-- 
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:[~2001-05-14 16:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-14 14:55 (Fwd) " Bart Schaefer
2001-05-14 15:23 ` Peter Stephenson
2001-05-14 16:21   ` Bart Schaefer [this message]
2001-05-14 18:09     ` Jason Price
     [not found]     ` <20010516130705.A25104@oobleck.gatech.edu>
     [not found]       ` <1010516194927.ZM15038@candle.brasslantern.com>
2001-05-16 21:24         ` Jason Price
  -- strict thread matches above, loose matches on Subject: below --
2001-03-29  9:51 Sven Wischnowsky
2001-03-29  6:53 Bart Schaefer
2001-03-29 10:19 ` Peter Stephenson
2001-03-29 11:27 ` Peter Stephenson
2001-03-29 14:36 ` Peter Stephenson

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=1010514162145.ZM10006@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=jprice@CyberBuzz.GaTech.edu \
    --cc=zsh-workers@sunsite.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).