From: Noa Resare <noa@resare.com>
To: rhug-rhats@sources.redhat.com
Subject: Re: segfault when running ant
Date: Tue, 16 Dec 2003 10:36:00 -0000 [thread overview]
Message-ID: <1071570993.18078.36.camel@dublin.kontoret> (raw)
In-Reply-To: <1070019719.27083.86.camel@ua-213-114-26-86.cust.bredbandsbolaget.se>
fre 2003-11-28 klockan 12.41 skrev Noa Resare:
> Yesterday i recompiled the naoko SRPMS on Fedora Core 1, and was able to
> enjoy the insane speed increase when using the resulting ant binary to
> build small ant projects.
>
> Howerver, when i try to do the same thing today ant dies with a
> segfault.
The reason for this was the nightly 'prelink' run:
[root@dublin tmp]# ant
Buildfile: build.xml does not exist!
Build failed
[root@dublin tmp]# /etc/cron.daily/prelink
[root@dublin tmp]# ant
Segmenteringsfel
The "correct" fix for this (other than disabling daily prelinking) is
beyond me to find. I'll leave that to the people @redhat.com :)
cheers/noa
prev parent reply other threads:[~2003-12-16 10:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-28 11:42 Noa Resare
2003-11-28 12:04 ` Gary Benson
2003-11-28 12:28 ` Noa Resare
2003-11-28 13:43 ` Gary Benson
2003-11-28 18:17 ` Jeff Sturm
2003-11-28 22:35 ` Noa Resare
2003-12-16 10:36 ` Noa Resare [this message]
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=1071570993.18078.36.camel@dublin.kontoret \
--to=noa@resare.com \
--cc=rhug-rhats@sources.redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).