From mint-bounce@lists.fishpool.fi Sat Jun 12 17:13:53 2010 Date: Sat, 12 Jun 2010 17:12:29 -0400 (EDT) From: Keith Scroggins To: m0n0 cc: =?UTF-8?Q?Vincent_Rivi=C3=A8re?= , mint@lists.fishpool.fi Subject: Re: [MiNT] Mixing binary code for different machine... is it =?UTF-8?Q?ok=3F?= In-Reply-To: Message-ID: References: <3a29599fd3dd0088076b2e1bd2c7b4d9-EhVcX1lFRQVaRwYcDTpQCEFddQZLVF5dQUBFBDBTXF5bVkYBV0F0CDpUX1hZQEcDX1Ne-webmailer2@server02.webmailer.hosteurope.de> <170beb6df97e2447489a8cc1584b5d3b-EhVcX1lFRQVaRwYcDTpQCEFddQZLVF5dQUBFBDBTXF5bVkYBV0F0CDpUX1hZQEcGX1Nc-webmailer2@server02.webmailer.hosteurope.de> <4C10A1DA.2070103@freesbee.fr> <314d421e3118ad59e08a01309083c1eb-EhVcX1lFRQVaRwYcDTpQCEFddQZLVF5dQUBFBDBTXF5bVkYBWkF0AFQ6XF1YR0YFW1xfRg==-webmailer2@server08.webmailer.hosteurope.de> <4C13EF11.5080906@freesbee.fr> <2148bf950abe0adde97bbd3daebf9117-EhVcX1lFRQVaRwYcDTpQCEFddQZLVF5dQUBFBDBTXF5bVkYBWkF0AFQ6XF1YR0YFWl1eRw==-webmailer2@server08.webmailer.hosteurope.de> <4C13F3C1.6030305@! freesbee.fr> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-559023410-2022861571-1276376883=:17012" Content-ID: X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: kws@radix.net Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. ---559023410-2022861571-1276376883=:17012 Content-Type: TEXT/PLAIN; CHARSET=X-UNKNOWN; FORMAT=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Content-ID: Its wrong? Or something else is? objdump -af /usr/lib/libc.a architecture: m68k:68020, flags 0x0000003f: objdump -af /usr/lib/libgmp.a architecture: m68k:68000, flags 0x0000003f: objdump -af /usr/lib/libmpfr.a architecture: m68k:68020, flags 0x0000003f: objdump -af /usr/lib/m5475/libssp.a architecture: m68k:68020, flags 0x0000003c: MiNTLib I believe compiles with -m68000 GMP Compiles with -m68000 MPFR Compiled with -m68000 That libssp was compiled with -mcpu=3D5475 And OpenSSL is compiled three times, with no CPU parameter which defaults= =20 to 68000, -m68020-60, and -mcpu=3D5475 Keith On Sat, 12 Jun 2010, m0n0 wrote: > > Am Samstag, den 12.06.2010, 22:53 +0200 schrieb Vincent Rivi=C3=A8re > : > >> MiKRO said that there is no big speed difference between code compiled > for >> 68000 and 68020, except for the FPU. I don't think OpenSSL use the FPU. >> What makes OpenSSL for 68000 impossible to use ? > > I meant: It's not possible to use it with an 68000 machine, at least > that's what > I was reading in some newsgroup. They said it would take hours to > establish the > connection ;) > > About the 68000 openssl version: > > when I do > objdump -af /usr/lib/libssl.a > > it spits out: > architecture: m68k:68020, flags 0x00000000: > > To me this seems like an version for 68020. How should I interpret this > output? > > Greets, > m0n0 > > ---559023410-2022861571-1276376883=:17012--