Mailing List Archive: gnupg for mipsel-linux

gnupg for mipsel-linux

Aug 6, 2001, 3:56 PM

Post #1 of 3 (928 views)

I bought an linux based palm organizer from agendacomputing. It's an
impressive device runing all kinds of linux services and demons (even
X) so gnupg should be no problem.

I ./configured the gnupg software and changed the makefiles by hand -
replacing gcc with mipsel-linux-gcc and /usr/mipsel-linux as lib-path.
It compiled until the -lz library was not found. In fact I could not
find it in the mipsel packages.

./configures --target= also didn't work, since I don't know what taret
the define. Can anyone help me with hints on possible modifications of
configure oder Makefile?

Thanks a lot,
Thomas

Re: gnupg for mipsel-linux [ In reply to ]

nisse at lysator

Aug 8, 2001, 2:00 AM

Post #2 of 3 (910 views)

Permalink

haensel99@t-online.de writes:

> ./configures --target= also didn't work, since I don't know what taret
> the define. Can anyone help me with hints on possible modifications of
> configure oder Makefile?

--target is used only for configuring compilers and similar tools.
It's the platform you want the built program to generate code for.
So it doesn't apply to gnupg.

What name of the platform was used when building your cross tools? For
example, when I build for palmos, I have a compiler called
m68k-palmos-gcc, and a directory under lib/gcc-lib/m68k-palmos. So the
name of that platform is "m68k-palmos".

I haven't tried compiling anything for the agenda yet, but if you have
the cross tools installed, you should be able to figure out the
canonical name for that platform in the same way.

When you have the name, use the --host flag to configure. And then
hope that gnupg supports cross compilation, I haven't tried.

Regards,
/Niels

Re: gnupg for mipsel-linux [ In reply to ]

wk at gnupg

Aug 8, 2001, 2:27 AM

Post #3 of 3 (920 views)

Permalink

On 08 Aug 2001 11:00:25 +0200, Niels Möller said:

> --target is used only for configuring compilers and similar tools.
> It's the platform you want the built program to generate code for.
> So it doesn't apply to gnupg.

BTW, the scripts/autoconf --build-w32 code used --target and it
worked. I fixed that while migrating to autoconf 2.52.

> When you have the name, use the --host flag to configure. And then
> hope that gnupg supports cross compilation, I haven't tried.

For Windows it works ;-). I have not tried any other hosts. There are
some assumptions in the code (watch out for "assuming foo" in the
configure log). So it should work for 32 bit little endian hosts.
There are one or two case statements in the configure script which can
be used to change values for certain hots (grep for "mingw32").

--
Werner Koch Omnis enim res, quae dando non deficit, dum habetur
g10 Code GmbH et non datur, nondum habetur, quomodo habenda est.
Privacy Solutions -- Augustinus