Re: Industrial computer
- From: Nix <nix-razor-pit@xxxxxxxxxxxxx>
- Date: Sat, 11 Feb 2012 23:08:57 +0000
On 11 Feb 2012, Gordon Henderson outgrape:
In article <87obt51nkd.fsf@xxxxxxxxxxxxxxxx>,[...]
Nix <$}xinix{$@esperi.org.uk> wrote:
One caveat: these CPUs are 32-bit-only, the end of a development line,
and not *quite* 686-compatible. GCC has long taken care not to produce
the missing instruction (a long NOP, "nopl 0x0(%rax)", 0f 1f 40 00), but
binutils was not so careful, and until early last year GNU as produced a
long NOP for alignment purposes if -mtune=i686 was passed to it: GCC
doesn't pass it that flag, but glibc does, leading to a libc_nonshared.a
that crashes binaries linked against that glibc. see e.g.
<https://bugzilla.redhat.com/show_bug.cgi?id=579838>, fixed by
<http://sourceware.org/bugzilla/show_bug.cgi?id=6957>.
Every distributor out there has fixed this by now, thankfully, but you
might still get bitten if someone builds a glibc against a sufficiently-
old binutils.
Not had an issue - so-far, but I compile asterisk, apache & php from
source using the right compiler flags. My base is Debian.
Debian fixed this some months ago. You'll only see this if you compile
*glibc* from source, but that sort of thing is relatively common with
embedded systems :) (mine is cross-compiled from source: the resulting
tree is rsynced over from the compilation host every night.)
--
NULL && (void)
.
- References:
- Industrial computer
- From: Folderol
- Re: Industrial computer
- From: Folderol
- Re: Industrial computer
- From: Gordon Henderson
- Re: Industrial computer
- From: Nix
- Re: Industrial computer
- From: Gordon Henderson
- Industrial computer
- Prev by Date: Re: Industrial computer
- Next by Date: Re: Album art downloader
- Previous by thread: Re: Industrial computer
- Next by thread: Re: Industrial computer
- Index(es):
Relevant Pages
|