From: "Kevin D. Kissell" <kevink@paralogos.com>
To: Klatt Uwe <U.Klatt@miwe.de>
Cc: "'linux-mips@linux-mips.org'" <linux-mips@linux-mips.org>
Subject: Re: Same mipsel binary für 2.4 and 2.6 kernel possible?
Date: Fri, 19 Sep 2008 15:28:41 +0200 [thread overview]
Message-ID: <48D3A909.6020604@paralogos.com> (raw)
In-Reply-To: <A1F06CF959C7E14EAC28F277F368175805686A8D6D@MAS15.arnstein.miwe.de>
When you say "float math isn't working", what do you mean? When you say
that the new binary
only works with the 2.6 kernel, what do you mean? Are you getting bad
answers, or is the program
crashing? If it's crashing, and you run it under gdb, where is it
blowing up, and why? Are you able
to re-create the "old" binary? If you do a static link of the program
using the old tools,
does the resulting binary work better under 2.6?
The FPU emulator has bad some minor cleanup over the past few years, but
it's been pretty
stable, and I can't recall having seen any serious functional or
compatibility problems in a long
time. I think it's more likely that you've got a problem with libraries
and/or build procedures
for the application.
Regards,
Kevin K.
Klatt Uwe wrote:
> Hello,
>
> I have a custom hardware (AU1100) with kernel 2.4 and an working binary using floats (compiled with gcc 3.3.5).
> Now I am testing with kernel 2.6.
>
> When I use the old binary, float math isn't working anymore.
> I have to recompile the source with new gcc 4.1.2 but then the new binary is working only on kernel 2.6.
>
> Can somebody give me some hints, how to chage settings for kernel 2.6 creation or compiler settings to generate an universal binary.
>
> Thanks
> Uwe
>
>
>
next prev parent reply other threads:[~2008-09-19 13:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-19 7:58 Same mipsel binary für 2.4 and 2.6 kernel possible? Klatt Uwe
2008-09-19 9:42 ` [SPAM] " Markus Gothe
2008-09-19 10:34 ` Ralf Baechle
2008-09-19 10:56 ` AW: " Klatt Uwe
2008-09-19 13:28 ` Kevin D. Kissell [this message]
2008-09-19 13:40 ` Klatt Uwe
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=48D3A909.6020604@paralogos.com \
--to=kevink@paralogos.com \
--cc=U.Klatt@miwe.de \
--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