From: email@example.com (Lord Doomicus)
Subject: [TUHS] /usr/bin/bs on HPUX?
Date: Wed, 17 Dec 2008 18:55:24 -0500 [thread overview]
Message-ID: <E3303491-1270-4852-AE27-C76E7E68085C@mac.com> (raw)
On Dec 17, 2008, at 11:35 AM, John Cowan wrote:
> lyricalnanoha scripsit:
>> it's using a very bizarre form of longjmp()... was that the normal
>> in sys3? it's using a struct, instead of the two parameters glibc
> v7 wants two parameters too. This was probably some attempt at
> cleanup that
> didn't survive.
> To fork a hacker nursery rhyme:
> System III! System III!
> See how it runs! See how it runs!
> Its longjmp() loses so totally,
> It runs all its programs in 'I & D',
> It's made by our fav'rite monopoly,
> System III!
Yea, I got the same thing when I tried compile it under OS X. I know
HPUX has it, so I checked the man page for longjmp under HPUX, and
like OS X, it takes two parameters. So, someplace, there is a version
of the bs source that has the correct longjmp system call. But, it
may only be in the HPUX source tree. I should boot up one of my SGI's
and have a look to see if it has bs, and what version of longjmp it
Derrik Walker v2.0, RHCE
lorddoomicus at mac.com
"There's nothing nice about Steve Jobs and there's nothing evil about
-- Chuck Peddle, MOS 6502 Chip Designer
-------------- next part --------------
An HTML attachment was scrubbed...
next prev parent reply other threads:[~2008-12-17 23:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-17 14:27 Jose R. Valverde
2008-12-17 15:39 ` John Cowan
2008-12-17 16:14 ` lyricalnanoha
2008-12-17 16:35 ` John Cowan
2008-12-17 23:55 ` Lord Doomicus [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-12-10 0:30 Lord Doomicus
2008-12-10 9:45 ` Tim Bradshaw
2008-12-10 14:29 ` Jason Stevens
2008-12-10 18:08 ` John Cowan
2009-01-09 10:51 ` Andrzej Popielewicz
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).