From: Wolfgang Denk <wd@denx.de>
To: "Michael Carey" <MCarey@nearfield.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: ELDK 3.1.1 support for x86_64 host architecture
Date: Fri, 04 Aug 2006 22:11:26 +0200 [thread overview]
Message-ID: <20060804201127.00D2D352640@atlas.denx.de> (raw)
In-Reply-To: Your message of "Thu, 03 Aug 2006 17:11:31 PDT." <44D22E43020000710000243E@webmail.nearfield.com>
In message <44D22E43020000710000243E@webmail.nearfield.com> you wrote:
> I found the subject "ELDK 3.1.1 support for x86_64 host architecture" in the archives (Apr 15 2005) which describes my problem, however there was never any posting of a resolution.
There was none, as there is no problem. ELDK 3.1.1 (and later
versions) runs fine on x86_64 hosts, assuming you're using any sane
Linux distribution. For example:
-> ppc_8xx-gcc -v
Reading specs from /opt/eldk-3.1.1/usr/bin/../lib/gcc-lib/ppc-linux/3.3.3/specs
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --with-newlib --enable-languages=c,c++ --disable-libgcj --host=i386-redhat-linux --target=ppc-linux
Thread model: posix
gcc version 3.3.3 (DENX ELDK 3.1.1 3.3.3-9)
------------------------^^^^^^^^^^
-> uname -a
Linux pollux.denx.de 2.6.10-1.771_FC2smp #1 SMP Mon Mar 28 01:05:47 EST 2005 x86_64 x86_64 x86_64 GNU/Linux
-----------------------------------------------------------------------------^^^^^^
-> cat /etc/issue
Fedora Core release 2 (Tettnang)
...
> package rpm-4.1.1-1.8xa_10 is intended for a i386 architecture
Your Linux distro is kind of broken.
> The details on my system are:
...
> Welcome to SUSE LINUX 10.1 (X86-64) - Kernel \r (\l).
Yes, SuSE has always found interesting ways to break compatibility.
That's why I avoid it. IIRC, SuSE provides a special tool "linux32"
which has to be used to run 32-bit applications on a x86_64 system.
Don't ask me why they need it. Other distros run the 32-bit
applications just fine without such intricacy.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
There are very few personal problems that cannot be solved through a
suitable application of high explosives.
next prev parent reply other threads:[~2006-08-04 20:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-04 0:11 ELDK 3.1.1 support for x86_64 host architecture Michael Carey
2006-08-04 20:11 ` Wolfgang Denk [this message]
2006-08-04 20:43 ` Frank
2006-08-05 19:32 ` Wolfgang Denk
2006-08-04 21:00 ` Ben Warren
-- strict thread matches above, loose matches on Subject: below --
2006-08-07 17:22 Michael Carey
2005-04-14 21:09 larry_chen
2005-04-13 22:35 larry_chen
2005-04-14 5:48 ` Wolfgang Denk
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=20060804201127.00D2D352640@atlas.denx.de \
--to=wd@denx.de \
--cc=MCarey@nearfield.com \
--cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).