User Feedback :: Great but could someone help a little bit

Packages that are meant for that distro are easy to install. Deb's are meant for Debian, and with that they are easy to install.

Compiling might prove easier

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.

Lcrypto problem (continued)

Many thanks Juanito / Curaga for your help again.

Apologies for not being tuned in for a few days - work took me away.

I think I might well be suffering from 'a little knowledge is a bad thing!'. I am getting to understand this all a lot better but I am still essentially at sqaure one with this partiuclar problem.

Juanito - I understand that I can specify where to get the libraries (LDFLAGS) I just don;t know which libraries to put in the folder I am specifying. The libcrypt.2.3.0.so available in the lib folder I believe is a runtime version of the library I need. You mentioned before using a switch which enabled the use of runtime libraries for compilation - unfortunately I can't see any reference to this in ./configure --help for rdesktop. Is this a setting that can be used for all compilations?

Many thanks

C.

Quote

I understand that I can specify where to get the libraries (LDFLAGS) I just don;t know which libraries to put in the folder I am specifying.

- Usually when you run ./configure, it tells you which libraries you're missing.

Quote

You mentioned before using a switch which enabled the use of runtime libraries for compilation

- sorry I wasn't clear, what I meant was there's often a ./configure switch to tell the compiler to build static or dynamic libraries.

Maybe this can be done one step at a time - can you cut & paste the first error you get when you run ./configure?

In order not to complicate things just yet, I have added no export flag settings (CDFLAGS LDFLAGS) - this is the ./configure output.

$ ./configure
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for a BSD-compatible install... /usr/bin/install -c
checking how to run the C preprocessor... gcc -Echecking for egrep... grep -E
checking for ANSI C header files... yes
checking whether byte ordering is bigendian... no
checking for X... libraries /usr/X11R6/lib, headers
checking for gethostbyname... yes
checking for connect... yes
checking for remove... yes
checking for shmat... yes
checking for IceConnectionNumber in -lICE... yes
checking for library containing socket... none required
checking for library containing inet_aton... none required
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking sys/select.h usability... yes
checking sys/select.h presence... yes
checking for sys/select.h... yes
checking sys/modem.h usability... no
checking sys/modem.h presence... no
checking for sys/modem.h... no
checking sys/filio.h usability... no
checking sys/filio.h presence... no
checking for sys/filio.h... no
checking sys/strtio.h usability... no
checking sys/strtio.h presence... no
checking for sys/strtio.h... no
checking locale.h usability... yes
checking locale.h presence... yes
checking for locale.h... yes
checking langinfo.h usability... yes
checking langinfo.h presence... yes
checking for langinfo.h... yes
checking for strip... strip
checking for OpenSSL directory... /usr
checking if architecture needs alignment... yes
checking ao/ao.h usability... no
checking ao/ao.h presence... no
checking for ao/ao.h... no
checking sys/soundcard.h usability... yes
checking sys/soundcard.h presence... yes
checking for sys/soundcard.h... yes
checking dmedia/audio.h usability... no
checking dmedia/audio.h presence... no
checking for dmedia/audio.h... no
checking sys/audioio.h usability... no
checking sys/audioio.h presence... no
checking for sys/audioio.h... no
checking for dirent.h that defines DIR... yes
checking for library containing opendir... no
checking for dirfd... no
checking whether dirfd is declared... yes
checking whether dirfd is a macro... no
checking iconv.h usability... yes
checking iconv.h presence... yes
checking for iconv.h... yes
checking for iconv... no, consider installing GNU libiconv
checking for socklen_t... yes
checking sys/vfs.h usability... yes
checking sys/vfs.h presence... yes
checking for sys/vfs.h... yes
checking sys/statvfs.h usability... yes
checking sys/statvfs.h presence... yes
checking for sys/statvfs.h... yes
checking sys/statfs.h usability... yes
checking sys/statfs.h presence... yes
checking for sys/statfs.h... yes
checking sys/param.h usability... yes
checking sys/param.h presence... yes
checking for sys/param.h... yes
checking for sys/mount.h... yes
configure: checking how to get filesystem space usage...
checking statvfs64 function (SVR4)... no
checking statvfs function (SVR4)... no
checking for 3-argument statfs function (DEC OSF/1)... checking for two-argument statfs with statfs.bsize member (AIX, 4.3BSD)... no
checking for four-argument statfs (AIX-3.2.5, SVR3)... no
checking for two-argument statfs with statfs.fsize member (4.4BSD and NetBSD)... no
checking for two-argument statfs with struct fs_data (Ultrix)... no
checking for struct statfs.f_namemax... no
checking for struct statvfs.f_namemax... yes
checking for struct statfs.f_namelen... yes
checking for struct statvfs.f_namelen... no
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... 64
checking for _LARGE_FILES value needed for large files... no
checking mntent.h usability... yes
checking mntent.h presence... yes
checking for mntent.h... yes
checking for setmntent... no
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
configure: creating ./config.status
config.status: creating Makefile

Next Page...
original here.