Re: 1 new message in 1 topic - digest
Father Gordon Gilbert
Thanks for the help so far. I haven't tried anything you suggested in your reply, because they sound too geekish for me. But here are some answers to the questions you wrote:
1. My ports tree is via cvsup. My son is one of the maintainers, and he has always said that when I want to upgrade anything, I should have the latest ports --
2. So my latest cvsup was within a week before installing (well, portupgrading -- much the same I think) Krusader 1.70
3. I don't do any self-compiling (except for Lilypond, and their stuff is really easy). KDE and all other programs are installed via ports if I do them, and even my son does it this way 99.9% of the time.
4. KDE version is the latest (2.5.3), because I upgraded that since the install of the non-working Krusader. QT is version 3.3.5
5. KCrash did not come up. The only thing I got was a "core dump" line in the xterm.
6. I don't have the complete KDE system running -- I use FVWM2 as my window manager (simple, but I like it) and so I use XTerms when I need something like that. No helpful info came from that. Here's what happens when I do that:
Segmentation fault (core dumped)
So, I'm at the end of my rope here -- can you help? Should I make deinstall, elimiate the distfile, and start again? Maybe I'll try that. Meanwhile, I appreciate your looking at my answers above and seeing what help you can be.
Blessings,
Father Gordon Gilbert+
krusader-users
http://groups.google.com/group/krusader-users
krusade...@googlegroups.com
Today's topics:
* 2 new messages in 1 topic - digest - 1 messages, 1 author
http://groups.google.com/group/krusader-users/browse_thread/thread/18124ee191a4608
==============================================================================
TOPIC: 2 new messages in 1 topic - digest
http://groups.google.com/group/krusader-users/browse_thread/thread/18124ee191a4608
==============================================================================
== 1 of 1 ==
Date: Sat, Sep 2 2006 9:19pm
From: Heiner
On Friday 01 September 2006 02:19, Father Gordon Gilbert wrote:
> Hi again folks,
>
> Thanks for your help, Csaba. But I've come to a problem already. I
> downloaded the file, then did the tar, but when I did the next step, it
> said "autoconf not found" so I looked for that, and I have two versions of
> autoconf, both newer than required. Am I in the wrong dir or something?
Hi!
Please note, that FreeBSD differs from linux a bit here. In FreeBSD there is
no default autoconf. So I first apply the attached patch to the cvs. It
requires
7of9# ls /var/db/pkg | grep auto
autoconf-2.59_2
automake-1.9.6
to be installed. Others might work as well, but then you need to adjust the
patch. The actual build I do with the attached following script.
But this is for development only. Ordinary user should stuck to the port
system, which does all the magic for you.
Currently 1.70.1 is in the port system. I do not know, where you got a
1.70.0_1 from - this should never have been existed!
To further track down your problems, the following questions may help:
- where did you get your port tree from? From a cd or via cvsup?
- when have you updated your ports tree last time?
- how did you install kde & friends? Self compiled or from the binary
packages?
- what are the installed qt/kde versions?
- did the crash give a usefull KCrash message? If KCrash did not come up or
contains mainly question marks, the answer is no
- could you create a back trace? To do so, start krusader from the konsole via
/usr/local/bin/krusader --nocrashhandler
After the crash, go into the directory with the .core file and type
gdb -c krusader.core /usr/local/bin/krusader
On the command prompt, type bt followed by enter.
Maybe that you must press enter some times now. The whole output is of
interest.
Heiner
export QTDIR=/usr/X11R6
export KDEDIR=/usr/local
#export CXXFLAGS="-Wcast-align -Wconversion -Wchar-subscripts"
make -f Makefile.cvs && libtoolize --force && ./configure --enable-debug=full --build=i386-portbld-freebsd5.5 --build=i386-portbld-freebsd5.5 --x-libraries=/usr/X11R6/lib --x-includes=/usr/X11R6/include --disable-as-needed --with-qt-includes=/usr/X11R6/include --with-qt-libraries=/usr/X11R6/lib --with-extra-libs=/usr/local/lib --with-extra-includes=/usr/local/include --prefix=/usr/local && touch config.h.in && gmake && krusader/krusader
==============================================================================
You received this message because you are subscribed to the Google Groups "krusader-users"
group.
To post to this group, send email to krusade...@googlegroups.com or visit http://groups.google.com/group/krusader-users
To unsubscribe from this group, send email to krusader-user...@googlegroups.com
To change the way you get mail from this group, visit:
http://groups.google.com/group/krusader-users/subscribe
To report abuse, send email explaining the problem to ab...@googlegroups.com
==============================================================================
Google Groups: http://groups.google.com
Heiner
> 1. My ports tree is via cvsup. My son is one of the maintainers, and he
> has always said that when I want to upgrade anything, I should have the
> latest ports --
Well, you might grep an inconsistent state this way. But I do the same - so
probably no problem here. Note, that cvsup updates the ports only - the
installed software is not affected by this! To upgrade usually portupgrade is
been used.
> 2. So my latest cvsup was within a week before installing (well,
> portupgrading -- much the same I think) Krusader 1.70
ls /var/bd/pkg | grep krusader
will tell
> 3. I don't do any self-compiling (except for Lilypond, and their stuff is
> really easy). KDE and all other programs are installed via ports if I do
> them, and even my son does it this way 99.9% of the time.
This is a more imprtant question: how do upgrade the ports? I guess via
portupgrade. Do you use the -P or -PP switch? If so, portupgrade is
downloading compiled packages and installes them. If not it downloades the
source codes and does the compilation for you.
> 4. KDE version is the latest (2.5.3), because I upgraded that since the
> install of the non-working Krusader. QT is version 3.3.5
I guess you mean 3.5.3.
ls /var/db/pkg | grep kde
will tell
> 5. KCrash did not come up. The only thing I got was a "core dump" line in
> the xterm.
This is because of fvwm I guess
> 6. I don't have the complete KDE system running -- I use FVWM2 as my
> window manager (simple, but I like it) and so I use XTerms when I need
> something like that. No helpful info came from that. Here's what happens
> when I do that:
That *might* be an issue. I never tried krusader under fvwm2. But on the other
hand it worked before and I do not know, what change might have stopped this.
I am not sure how to continue. One idea might be to leave the system as it is
but to go back to the krusader version, which was working (to see if it still
does). The "how" depends on the answers on the questions above.
The other is to analyze the core dump. If you go (with xterm) into the
directory you started krusader from, what does
ls -l *.core
show? And what does
ls -l /usr/local/bin/krusader
show?
Heiner