Re: compiling problem
Re: compiling problem
- Subject: Re: compiling problem
- From: Steve Checkoway <email@hidden>
- Date: Wed, 29 Mar 2006 00:56:15 -0800
On Mar 29, 2006, at 12:41 AM, anil kumar dahiya wrote: Hi Kenny Abt First comment: I am sure its not coming out of loop etc.
test.c: In function `main':
test.c:95: warning: control reaches end of non-void function
That's where you're reaching the end of main without returning anything. That coupled with the other warning leads me to suspect that you've defined main as: main( int argc, char *argv[] ) { /* ... */ } without a return type.
Abt Second Comment: I have compiled client program using Litle Endian byte order so if client is working fine on linux intel machine .....then why is not working on mac os machine ?
gcc -ansi -DOPENSSL_THREADS -D_REENTRANT -DOPENSSL_NO_KRB5 -O3 -fomit-frame-pointer -fno-common -DL_ENDIAN -Wall -lssl -lcrypto -o test test.c You've defined L_ENDIAN but that is just a macro, that's not actually changing the powerpc to be little endian. As pointed out, powerpc is big endian. There's nothing you can do (or define) to change that. You have to swap bytes yourself. Is my CFLAGS are fine on macos ? Well, you've defined OPENSSL_THREADS, _REENTRANT, OPENSSL_NO_KRB5 and L_ENDIAN , I assume that's doing what you want. I'm not sure that -fomit-frame-pointer actually does anything on a powerpc since several docs (both Apple and IBM) mention that it doesn't use a frame pointer. -fno-common is an odd choice though. From the gcc man page:
The only reason this might be useful is you wish to verify that the program will work on other systems which always work this way.
You probably don't want that, but I'm not an expert, I've never used it.
- Steve
|
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden