cross-compiling to mipsel

Dirk Stoecker gcrypt at
Fri Feb 24 09:09:38 CET 2006

On Thu, 23 Feb 2006, Daniel Eiband wrote:

> Am Donnerstag 23 Februar 2006 18:08 schrieben Sie:
> > I had an equal problem. The --with-gpg-error-prefix seems not to work as
> > expected. I used following method after looking in the configure file
> > (assuming libgpg-error is a subdirectory in current dir):
> >
> > export GPG_ERROR_CONFIG=`pwd`/libgpg-error/src/gpg-error-config
> > export CPPFLAGS=-I`pwd`
> > export LDFLAGS=-L`pwd`
> > ln -sf libgpg-error/src/.libs/libgpg-error.a .
> > ln -sf libgpg-error/src/gpg-error.h .
> >
> > In current dir (`pwd`) now are the links to the .a file and the .h file of
> > gpg-error, thats why the include paths point to this.
> >
> > ./configure --with-gpg-error-prefix=dummy ...
> --with-gpg-error-prefix is the prefix where you installed gpg-error. It seams 

It probably should be, but it is not. Read the autogenerated ./configure 
file to understand why I use the environment variable and set 
--with-gpg-error-prefix to dummy. It took me some time to understand, why 
--with-gpg-error-prefix did not work as expected and how to work around.

> like you didn't install it at all. Besides, this is not my problem. 

Excactly. I did not INSTALL it, but compiled a local copy of gpg-error. 
This is usually what you need for cross compiling also (at least in static 
mode). In dynamic mode you need to do some path magic to get it to work on 
you destination system as well.

-- (PGP key available)

More information about the Gcrypt-devel mailing list