Thx for the tips!

I'll admit I have tried the "-R" stuff in the past yet things did not 
work out as I expected/understood they should so I sort of gave up on 
using that flag. From what I have read though it should have solved some 
of the relocation errors I have received at times during linking yet 
maybe I was not using it correctly??

Also to disclaim, I have an SA/DBA/Security background and I am not a 
developer per se so I'll admit right off that when it comes to 
compiling/building code I am more of a trial & error hacker 
(non-security definition) than a true developer like you folks are . . ;-)

I'll holler if I get stumped with the gnu tsl stuff yet I think I might 
already have that stuff on my dev system, can't remember right now . . .

Thx!

T.

Ben Taylor wrote:

>---- "Thomas D. Briglia" <briglia at stanford.edu> wrote: 
>  
>
>>Nice work with SDL, it compiled no problem, and I did not even have to 
>>read the README! ;-)
>>    
>>
>
>Since you're on Solaris 10, there is one dependency that I documented
>last night which is for gnu tsl (transport security layer) which requires
>pkg-config.  
>
>I compiled it up on my Solaris 9/X86 box, but had to do a pkg-get -i gnutls
>and pkg-get -i pkgconfig, but it all compiled right up.
>
>  
>
>>Actually first time it crapped out for I do not have audio enabled on my 
>>servers yet as soon as I deactivated audio in the configuration phase it 
>>compiled 64 bit no prob w/o a single Blastwave package, totally native 
>>Solaris dev env! ;-)
>>    
>>
>
>Audio on a server is not something you'd expect to see  :-)
>
>  
>
>>My normal dev env looks like:
>>
>>PATH=/usr/sfw/bin:/usr/bin:/usr/local/bin:/usr/ccs/bin:/usr/sbin:/usr/local/apr/bin:/usr/ucb:/usr/local/ldapcsdk-6.02/bin
>>LDFLAGS=-m64 -L/usr/local/ldapcsdk-6.02/lib -L/usr/local/ssl/lib 
>>-L/usr/local/lib/sasl2 -L/usr/local/lib
>>    
>>
>
>If you don't want to have any problems, I'd suggest adding -R flags for
>all the -L flags you have.
>
>  
>
>>CPPFLAGS=-m64 -I/usr/local/ldapcsdk-6.02/include 
>>-I/usr/local/ssl/include -I/usr/local/include/gssapi 
>>-I/usr/local/include/sasl2
>>    
>>
>
>
>Well, QEMU configure overrides the CFLAGS and CPPFLAGS
>to make sure that it gets the flags it expects.
>
>I'm pretty sure
>
>LD_LIBRARY_PATH=/usr/local/ldapcsdk-6.02/lib:/usr/lib/sasl2:/usr/local/BerkeleyDB.4.6/lib:/usr/local/ssl/lib:/usr/local/lib/sparcv9:/usr/sfw/lib/sparcv9:/usr/lib/sparcv9:/usr/local/lib:/usr/sfw/lib:/usr/lib:/usr/local/apr/lib
>  
>
>>LD_LIBRARY_PATH_64=/usr/local/ldapcsdk-6.02/lib:/usr/lib/sasl2:/usr/local/BerkeleyDB.4.6/lib:/usr/local/ssl/lib:/usr/local/lib/sparcv9:/usr/sfw/lib/sparcv9:/usr/lib/sparcv9:/usr/local/apr/lib:/usr/local/lib
>>    
>>
>
>Dump LD_LIBRARY_PATH.  See above about -R flags (this adds runtime lookups
>for the libraries so you don't have to carry around a LD_LIBRARY_PATH).
>
>see this http://xahlee.org/UnixResource_dir/_/ldpath.html for an explanatation.
>
>  
>
>>CFLAGS=-mcpu=v9 -m64 -O
>>LDSHARED=gcc -G -mcpu=v9 -m64
>>CXXFLAGS=-m64
>>CC=gcc -m64
>>CXX=g++ -m64
>>SASL_PATH=/usr/lib/sasl2
>>PKG_CONFIG_PATH=/usr/local/ssl/lib/pkgconfig:/usr/local/lib/pkgconfig:/usr/sfw/lib/pkgconfig
>>
>>Later on I will compile QEMU. If it goes as smoothe as SDL, then a 
>>double Kudos to you and all the other developers!
>>    
>>
>
>If you're on Solaris 10, it should just build.  
>
>If you're going to use the VNC features of QEMU, then you'll want to also build
>out GNU tls, opencdk, pgp and libpgp_error to enforce better security for the
>VNC passwords that get pushed across the network.
>
>Ben
>  
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://mail.opensolaris.org/pipermail/qemu-discuss/attachments/20071212/f147497f/attachment.html>

Reply via email to