To get the full picture, look into changes I have made in 'aspseek_solaris' CVS branch. For example:
cvs -z9 diff -u -r v_1_2_9 -r aspseek_solaris > sol.diff
(I have forked aspseek_solaris off 1.2.9pre, not 1.2.9, therefore some changes in diff you will get are irrelevant).
Gregory Kozlovsky wrote:
Kir, thank you for the info. Now, is this (int *) to (char *) assignment confined to some specific place? And is it always (int *) to (char )? If you can orient me, I can do the code modification myself.Gregory Kozlovsky Project Manager for Information Systems Tel: +41 (0)1 632 63 70 International Relations and Security Network (ISN) Fax: +41 (0)1 632 14 13 Center for Security Studies Email: [EMAIL PROTECTED] ETH Z�rich (Swiss Federal Institute of Technology Zurich) http://www.isn.ch/ Leonhardshalde 21, ETH-Zentrum / LEH CH-8092 Z�rich, Switzerland -----Original Message----- From: Kir Kolyshkin [mailto:[EMAIL PROTECTED]] Sent: Dienstag, 7. Januar 2003 12:00 To: [EMAIL PROTECTED] Subject: Re: [aseek-users] SUN Gregory Kozlovsky wrote:Hello, all, Did somebody managed to compile and use ASPseek on a SUN server withSolaris9?
As I have already mentioned before, ASPseek do not work on hardware that doesn't support unaligned memory access. SUN servers are among them. So,
compiling ASPseek successfully do not yet means it will work.
To check your system, compile and run a simple program:
#include <stdio.h>
int main(void)
{
int i = 1234;
char * cp = (char *)&i;
char j = *(cp + 1);
printf("%d\n", j);
}
On my box, result is 4. It can be different on arch that has a different byte order, but if you will receive "Bus error" or something like that,
that means ASPseek will not work on your arch.
I have managed to almost fix it (in a separate CVS branch named aspseek_solaris), but the work is not finished. To finish it, I need some expressed interest from somebody who wants to run ASPseek on Solaris.
