From: Matej Kupljen <matej.kupljen@ultra.si>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Re: MIPS LE build problems
Date: Thu, 18 Aug 2005 10:42:57 +0200 [thread overview]
Message-ID: <1124354577.13487.4.camel@localhost.localdomain> (raw)
In-Reply-To: <20050817080842.36E19353CFF@atlas.denx.de>
Hi
> So is there a clever way to "ask" gcc which endianess it's using?
> I tried to come up with one but failed so far...
I am searching how to do that.
How about if the config.mk runs a little test program, like
configure does?
For example:
#include <stdio.h>
#include <stdlib.h>
int main(int argc, char **argv)
{
unsigned int data = 0x01234567;
char *ptr = (char *)&data;
if (ptr[0] == 0x01 && ptr[1] == 0x23 && ptr[2] == 0x45 && ptr[3] == 0x67)
printf("big\n");
else if (ptr[3] == 0x01 && ptr[2] == 0x23 && ptr[1] == 0x45 && ptr[0] == 0x67)
printf("little\n");
else
printf("unknown\n");
return 0;
}
And then check the output of this program and decides to pass the -EL or -EB
to LDFLAGS.
Oh, do you know why I have to use the:
-Wa,-allow_branch_to_undefined
instead of:
-Wa,-mips_allow_branch_to_undefined
even though (I guess) I use the same patch as you do?
And why don't you accept the patch that eliminates this patch to
binutils?
BR,
Matej
next prev parent reply other threads:[~2005-08-18 8:42 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-08 21:13 [U-Boot-Users] MIPS LE build problems Wolfgang Denk
2005-08-09 16:59 ` [U-Boot-Users] " Thomas Lange
2005-08-09 19:47 ` Matej Kupljen
2005-08-09 20:56 ` Thomas Lange
2005-08-09 22:06 ` Thomas Lange
2005-08-09 23:23 ` Andrew Dyer
2005-08-10 6:06 ` Matej Kupljen
2005-08-10 6:52 ` Wolfgang Denk
2005-08-10 7:01 ` Matej Kupljen
2005-08-10 7:32 ` Wolfgang Denk
2005-08-10 7:43 ` Matej Kupljen
2005-08-10 8:45 ` Wolfgang Denk
2005-08-10 9:13 ` Matej Kupljen
2005-08-10 10:18 ` Wolfgang Denk
2005-08-17 7:07 ` Matej Kupljen
2005-08-17 8:08 ` Wolfgang Denk
2005-08-17 8:24 ` Matej Kupljen
2005-08-17 13:44 ` Wolfgang Denk
2005-08-18 6:31 ` Matej Kupljen
2005-08-18 8:46 ` Wolfgang Denk
2005-08-18 9:01 ` Matej Kupljen
2005-08-18 8:42 ` Matej Kupljen [this message]
2005-08-18 8:51 ` Wolfgang Denk
2005-08-18 9:08 ` Matej Kupljen
2005-08-18 19:54 ` Udi Finkelstein
2005-08-18 20:56 ` Wolfgang Denk
2005-08-19 8:59 ` Udi Finkelstein
2005-08-18 20:46 ` Wolfgang Denk
2005-08-19 4:55 ` Matej Kupljen
2005-08-18 18:31 ` Jerry Van Baren
2005-08-10 6:05 ` Matej Kupljen
2006-07-22 18:47 ` [U-Boot-Users] " Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2005-08-18 21:38 [U-Boot-Users] " Wolfgang Denk
2005-08-18 23:11 ` Zachary Landau
2005-08-18 23:28 ` Wolfgang Denk
2005-08-20 7:51 ` Matej Kupljen
2005-08-22 8:53 ` Leif Lindholm
2005-08-22 8:59 ` Wolfgang Denk
2005-08-24 8:54 ` Matej Kupljen
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=1124354577.13487.4.camel@localhost.localdomain \
--to=matej.kupljen@ultra.si \
--cc=u-boot@lists.denx.de \
/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