Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Kumba <kumba@gentoo.org>
To: linux-mips@linux-mips.org
Subject: Re: OpenSSL/Binutils Issues
Date: Sat, 10 May 2003 15:30:46 -0400	[thread overview]
Message-ID: <3EBD5366.70705@gentoo.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1076 bytes --]


It's attached in gzip format, as there was quite a bit of a return. 
Many assertion fails and invalid symbol indexes.

Let me know if you need anything more.

--Kumba


Thiemo Wrote:
>Kumba wrote:
[snip]
>> 	Which builds fine.  Then the error hits when attempting to execute 
>> 	the "conftest" executable:
>> 
>> 		./conftest: error while loading shared libraries:
>> 		usr/lib/libcrypto.so.0.9.6: unexpected reloc type 0x68
>
> This libcrypto seems to be broken. 0x68 is not a valid MIPS reloc type
> at all, and a shared lib should use only R_MIPS_32 (type 2) relocations
> anyway.

>> 	Has anyone seen anything like this?  My base mips install on my SGI 
>> Indigo2 is built using binutils-2.13.90.0.16, which builds everything 
>> fine, just doesn't cooperate well with -mips3 or higher options.  I'm 
>> not sure if this is mips-specific, or if I need to bother the OpenSSL 
>> team about it.
>
> It is probably a binutils issue. Can you send the output of
> objdump -R usr/lib/libcrypto.so.0.9.6 |grep R_MIPS |grep -v \(R_MIPS_32\|R_MIPS_NONE\)
> 
> 
> Thiemo









[-- Attachment #2: crypto-grep-mips.txt.gz --]
[-- Type: application/x-gzip, Size: 1304 bytes --]

             reply	other threads:[~2003-05-10 19:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-10 19:30 Kumba [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-10  4:20 OpenSSL/Binutils Issues Kumba
2003-05-10  5:50 ` Muthukumar Ratty
2003-05-10  5:50   ` Muthukumar Ratty
2003-05-10 14:19 ` Thiemo Seufer

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=3EBD5366.70705@gentoo.org \
    --to=kumba@gentoo.org \
    --cc=kumba12345@comcast.net \
    --cc=linux-mips@linux-mips.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