Juanito
Group: Members
Posts: 1601
Joined: Sep. 2005 |
 |
Posted: Sep. 23 2007,12:41 |
 |
My (non-expert) advice would be to try and compile the application yourself as Curaga suggests.
As you've found, your application will not compile because it depends on other applications. It's quite likely that some of these other applications will, in turn, depend on yet more applications - eventually you will get to the end of the dependency chain and then you can make a start.
My suggestion would be to compile everything to the same place and then you can use +/- the same commands to compile each time. Let's say you decide to use /opt/rdesktop, then you could use something like:| Code Sample | $ export CFLAGS=-I/opt/rdesktop/include
$ export LDFLAGS=-L/opt/rdesktop/lib
$ ./configure --help [to check application specific options]
$ ./configure --prefix=/opt/rdesktop [+app specific options]
$ make
$ touch mymarker
$ sudo make install
$ sudo find / -not -type 'd' -cnewer mymarker | grep -v "\/proc\/" | tee files |
The last line will make a list of the application files thus created in a file named "files". You can use this to create a master file list that will eventually be used to make your mydsl extension.
Since it looks like you're missing the crypto libraries/headers, you might need to start by compiling from the openssl-0.9.8e.tar.gz package, but that's just a suggestion (and I cannot remember if this package depends on anything else...).
Note: one common ./configure option I keep forgetting is the one to compile dynamic libraries (*.so) rather than static ones.
|
.
DSL Market ,
Great VPS hosting provided by Tektonic
