Hello Thomas
Linux does not use strings.h.
Linux only uses string.h.
SCO has it broke into 2 pieces
string.h strings.h.
That wouldn't cause a segfault.
Segfault is stepping on memory that doesn't
belong to you. Invalid pointer, etc.
Right now the splittering of Linux is an issue
for software developers. All Linux's are not
the same and behave quite differently.
Each Linux is like maintanining software
for a different OS entirely.
Tom Podnar at Microlite can give you some
insight on this and why Linux is not easy to
support.
I've had no experience with Mandriva.
I've stayed with SCO because there is
NO, one linux target to hit. I've played a little
with Suse 9 and 10 but not to build apps on.
The USLC compiler that SCO uses is a very
efficient compiler. We have to deal with a few "GCC" isms
we can't handle but most things compile fairly easily and run
faster than gcc compiled code.
We've had several issues over the past 2 years with
the Qt build that SCO had. We worked out most of
the issues with that now. Can you run Qt "designer", especially
the wizards without any problems?
I would suspect the Qt or KDE build more than I would
the Rekall code on Segfaults. What version of Qt are you
running and does that match what Rekall was built against?
The KDE build doesn't work well at this time on SCO.
A new KDE build is due to be released in October.
Give me some more details and I'll try to help.
After 30 years of coding COBOL, I'm quickly learning
C and C++ in depth. Slow process.
Paul
pmcnary@...
On Monday 20 August 2007 17:37, Thomas Spuhler wrote:
> Paul:
> Where is that file? Maybe the same issue with segfault
_______________________________________________
Rekall mailing list
Rekall@...
http://www.mailman.a-i-s.co.uk/cgi-bin/mailman/listinfo/rekall
