Date: Sun, 25 Apr 1999 12:32:11 +0200 From: Andreas Klemm <andreas@klemm.gtn.com> To: Aaron Granick <agranick@ucsd.edu>, Alex Zepeda <garbanzo@hooked.net> Cc: ports@FreeBSD.ORG Subject: Re: nasty problem to compile kirc-0.9.5-04 under FreeBSD 3.1-STABLE Message-ID: <19990425123211.B86837@titan.klemm.gtn.com> In-Reply-To: <000601be8e3d$6f27a150$d19b1e18@penguin.san.rr.com>; from Aaron Granick on Sat, Apr 24, 1999 at 03:30:11AM -0700 References: <19990424125248.A22812@titan.klemm.gtn.com> <Pine.BSF.4.05.9904241522160.292-100000@zippy.dyn.ml.org> <000601be8e3d$6f27a150$d19b1e18@penguin.san.rr.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Apr 24, 1999 at 03:30:11AM -0700, Aaron Granick wrote:
> I believe this is a problem because the KDE API has changed since kIRC was
> released...they moved the kdedir() function from public to protected status.
> Unfortunately, I haven't worked with KDE in some time so I don't know how to
> fix this error. You could replace the call with a hardcoded location for
> the KDE directory, or look it up as a shell variable, but there is probably
> a new 'official' way of retrieving the KDE directory path, but I dont' know
> what it is.
>
> Aaron
On Sat, Apr 24, 1999 at 03:23:28PM -0700, Alex Zepeda wrote:
> Aaron has for quite a while now wished to not receive mail concerning
> kIRC, and for that matter I'm no longer maintaining kIRC. It's no longer
> supported, and to compile it would require pre KDE 1.0 libs, and Qt 1.33.
Hi folks,
finally I got around this little failure, so that kirc compiles.
A script substitutes !!PREFIX!! just before compilation, so that
kirc port is fully location independent (just for the case that
a user wants a different installation path than /usr/local).
Additionally there was a '}' missing in DCC.cpp. Wonder how this
version could have been released, since kdcc was in fact not
compileable ;-)
--- kirc/defs.h.orig Sun Apr 25 11:43:46 1999
+++ kirc/defs.h Sun Apr 25 11:52:34 1999
@@ -5,6 +5,7 @@
#define IRC_CONFIG_H
#define APPNAME "kIRC"
+#define KDEDIR "!!PREFIX!!"
#define IRCDIR "share/apps/kirc"
#define ICONDIR "share/apps/kirc/icons"
#define IRCHOMEDIR ".kde/share/apps/kirc"
--- kirc/irc.cpp.orig Sun Apr 25 11:45:13 1999
+++ kirc/irc.cpp Sun Apr 25 11:47:56 1999
@@ -138,7 +138,7 @@
{
ParseArguments(argc, argv);
Settings::fileDir.sprintf("%s/%s", QDir::homeDirPath().data(), IRCHOMEDIR);
- Settings::sysFileDir.sprintf("%s/%s", KApplication::kdedir().data(), IRCDIR);
+ Settings::sysFileDir.sprintf("%s/%s", KDEDIR, IRCDIR);
app = new IrcApp( argc, argv, "kirc");
//signal (SIGSEGV, HandleSegFault); // redirect our segfaults
app->Go();
--- kdcc/DCC.cpp.orig Sun Apr 25 12:09:14 1999
+++ kdcc/DCC.cpp Sun Apr 25 12:09:33 1999
@@ -210,6 +210,7 @@
if (Settings::mode == "CHAT") {
debug(">connect %s %u", Settings::nick.data(), fd);
+ }
return fd;
}
But now after installation other (unexpected) problems arise.
andreas@titan{95} $ kirc
QPopupMenu: (unnamed) Popup has invalid menu item
QPopupMenu: (unnamed) Popup has invalid menu item
QPopupMenu: (unnamed) Popup has invalid menu item
QPopupMenu: (unnamed) Popup has invalid menu item
QPopupMenu: (unnamed) Popup has invalid menu item
QPopupMenu: (unnamed) Popup has invalid menu item
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 2
Abbruch (core dumped)
Exit 134
Perhaps this is the result of what you said, Alex, that
kirc perhaps really needs an older KDE version and an
older QT lib. Unfortunately we dropped the older QT version
in the FreeBSD ports collection, since no application seemed
to use/need it. During that time (when the decision has been
made), kirc already was flagged BROKEN, because of the compilation
errors ....
Now for me the question arises, if we should bring back qt1.33
and try it again to compile kirc ... or if not.
Sad but true ... as far as I see kirc seems to be a little
so to say -> unmaintained ...
Well, what's the status now ...
I saw in your signal handler code, that in case of an error the
user sees a messages, send me a bug report, etc ....
Just in case, we would bring kirc to run, is it wanted by the
author, to receive mails with bugreports ?
Or does the author not want to receive any messages about kirc,
so that it's really unmaintained ???
I'm not sure, but would it be perhaps a wise decision, to drop
perhaps kirc from the ports collection, since nobody maintains
it, and you know how users are, if things are not working
well ....
To sum it up ... what do _YOU_ think would be a good decision
for kirc in the FreeBSD ports collection ???
Or is there any taker, who could perhaps bring kirc to libqt 1.42
and KDE 1.1 ? [ Cc'd to ports ]
Andreas ///
--
Andreas Klemm http://www.FreeBSD.ORG/~andreas
http://www.freebsd.org/~fsmp/SMP/SMP.html
powered by Symmetric MultiProcessor FreeBSD
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990425123211.B86837>