public inbox for gentoo-embedded@lists.gentoo.org
 help / color / mirror / Atom feed
From: Tim Dodge <timmy@invisibles.org>
To: gentoo-embedded@lists.gentoo.org
Subject: [gentoo-embedded] openssl for arm
Date: Tue, 03 May 2005 21:42:52 +0100	[thread overview]
Message-ID: <4277E24C.1050006@invisibles.org> (raw)

Hi,

I'm trying to cross compile openssl-0.9.7e-r1 for arm-xscale-linux-uclibc.

It gets as far as crypto/md5 directory, and then chokes on the ASM like so:

making all in crypto/md5...
make[2]: Entering directory
`/var/tmp/portage/openssl-0.9.7e-r1/work/openssl-0.9.7e/crypto/md5'
arm-xscale-linux-uclibc-gcc -I.. -I../.. -I../../include -fPIC
-DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H
-DOPENSSL_NO_KRB5 -DL_ENDIAN -DTERMIO    -Wall -Os -pipe -march=armv5te
-mtune=xscale -Wa,--noexecstack -DSHA1_ASM -DMD5_ASM -DRMD160_ASM
-I/tmp/minime/usr/include  -c -o md5_dgst.o md5_dgst.c
arm-xscale-linux-uclibc-gcc -I.. -I../.. -I../../include -fPIC
-DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H
-DOPENSSL_NO_KRB5 -DL_ENDIAN -DTERMIO    -Wall -Os -pipe -march=armv5te
-mtune=xscale -Wa,--noexecstack -DSHA1_ASM -DMD5_ASM -DRMD160_ASM
-I/tmp/minime/usr/include  -c -o md5_one.o md5_one.c
(cd asm; /usr/bin/perl md5-586.pl elf -I.. -I../.. -I../../include -fPIC
-DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H
-DOPENSSL_NO_KRB5 -DL_ENDIAN -DTERMIO    -Wall -Os -pipe -march=armv5te
-mtune=xscale -Wa,--noexecstack -DSHA1_ASM -DMD5_ASM -DRMD160_ASM >
mx86-elf.s)
arm-xscale-linux-uclibc-gcc -c -I.. -I../.. -I../../include -fPIC
-DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H
-DOPENSSL_NO_KRB5 -DL_ENDIAN -DTERMIO    -Wall -Os -pipe -march=armv5te
-mtune=xscale -Wa,--noexecstack -DSHA1_ASM -DMD5_ASM -DRMD160_ASM  -o
asm/mx86-elf.o asm/mx86-elf.s
asm/mx86-elf.s: Assembler messages:
asm/mx86-elf.s:11: Error: alignment too large: 15 assumed
asm/mx86-elf.s:13: Error: unrecognized symbol type ""
asm/mx86-elf.s:15: Error: bad instruction `pushl %esi'
asm/mx86-elf.s:16: Error: bad instruction `pushl %edi'
asm/mx86-elf.s:17: Error: bad instruction `movl 12(%esp),%edi'

and so on, until:

asm/mx86-elf.s:684: Error: bad instruction `popl %esi'
asm/mx86-elf.s:685: Error: bad instruction `ret'
make[2]: *** [asm/mx86-elf.o] Error 1
make[2]: Leaving directory
`/var/tmp/portage/openssl-0.9.7e-r1/work/openssl-0.9.7e/crypto/md5'
make[1]: *** [subdirs] Error 1
make[1]: Leaving directory
`/var/tmp/portage/openssl-0.9.7e-r1/work/openssl-0.9.7e/crypto'
make: *** [sub_all] Error 1

I'm completely lost when it comes to assembly, any ideas what I can do
to get this to build?

Tim
-- 
gentoo-embedded@gentoo.org mailing list


             reply	other threads:[~2005-05-03 20:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-03 20:42 Tim Dodge [this message]
2005-05-03 20:50 ` [gentoo-embedded] openssl for arm Mike Frysinger
2005-05-04  1:21   ` Yuri Vasilevski
2005-05-04  1:30     ` Mike Frysinger
2005-05-04  2:07       ` Yuri Vasilevski
2005-05-04  2:25         ` Mike Frysinger
2005-05-04  3:05           ` Yuri Vasilevski
2005-05-13 17:18       ` Yuri Vasilevski
2005-05-15 17:39         ` Tim Dodge
2005-05-15 18:21           ` Yuri Vasilevski
2005-05-15 18:50             ` Tim Dodge
2005-05-04  9:15     ` Tim Dodge

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4277E24C.1050006@invisibles.org \
    --to=timmy@invisibles.org \
    --cc=gentoo-embedded@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox