From: LinuxPPC-Dev@associate.com
To: linuxppc-dev@lists.linuxppc.org
Cc: root@associate.com
Subject: Lock-up while building mod_perl
Date: 10 Apr 1999 14:53:03 -0000 [thread overview]
Message-ID: <19990410145303.1090.qmail@associate.com> (raw)
Hi,
Yesterday while trying to build/compile the mod_perl RPM from
ftp://rawhide.redhat.com/SRPMS/SRPMS/mod_perl-1.18-5.src.rpm
I experienced a total lock-up/freeze/crash. It's been a LONG while
since anything like that happened, so I thought I'd pass the new on here.
I have a suspicion that this may be connected to the glibc-p release,
which I recently upgraded to - this glibc also caused MySQL to stop working,
even when compiled against the new glibc.
Has anyone else seen this kind of problem (compiling mod_perl)?
I'm running on a 7200/90 updated with all the latest R4 stuff.
glen_stewart@associate.com
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
next reply other threads:[~1999-04-10 14:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-10 14:53 LinuxPPC-Dev [this message]
1999-04-10 20:19 ` Lock-up while building mod_perl Kevin B. Hendricks
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=19990410145303.1090.qmail@associate.com \
--to=linuxppc-dev@associate.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=root@associate.com \
/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.
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).