SCHAMANISMUS AUSBILDUNG
Unser Freund und Förderer der Inka-Schamane Juan aus Peru
Ausbildungs-Abschluss in Oberösterreich!
Die TeilnehmerInnen der Au
On 1/25/07, Mikael Pettersson <[EMAIL PROTECTED]> wrote:
There are many many many places where alignment is required,
and where incorrect alignment could cause almost random and
impossible to debug problems.
It is possible to enforce alignment with directives, the problem
is locating all the rel
Sergei Golovan writes:
> On 1/25/07, Mikael Pettersson <[EMAIL PROTECTED]> wrote:
> > The problem is still one of alignment. It seems that your M68K
> > toolchain doesn't align
> >
> > struct { int x; } var;
> >
> > to a 32-bit boundary. Whether that is the bug, or whether the
> > lock chec
On 1/25/07, Roman Zippel <[EMAIL PROTECTED]> wrote:
It's aligned, but unfortunately not as much as erlang liked.
Unfortunately that's also a very common error source in quite a few
packages, which then only fail on m68k.
We've found GCC option -malign-int for m68k. Citing from the manual:
Hi,
On Thu, 25 Jan 2007, Sergei Golovan wrote:
> Warning: if you use the -malign-int switch, GCC will align struc-
> tures containing the above types differently than most published
> application binary interface specifications for the m68k.
>
> Can the issue with
On 1/25/07, Mikael Pettersson <[EMAIL PROTECTED]> wrote:
The problem is still one of alignment. It seems that your M68K
toolchain doesn't align
struct { int x; } var;
to a 32-bit boundary. Whether that is the bug, or whether the
lock checker's alignment-of-static-data assumption is the bug,
I c
On Tue, Jan 23, 2007 at 10:39:11PM +0100, Petr Salinger wrote:
>
> >I am also tagging this bug "help" as I am waiting a patch from the m68k
> >porters to support thread local storage, as already asked on the
> >debian-m68k mailing list.
>
> As far as I know, only two places in glibc 2.5 require _
Sergei Golovan writes:
> On 1/25/07, Mikael Pettersson <[EMAIL PROTECTED]> wrote:
> > Definitely smells like a toolchain bug to me. In this case, since you've
> > enabled threads, erts_mtx_t is a properly declared struct type containing
> > among other things a pthread_mutex_t, an int, and a co
Hi,
On Thu, 25 Jan 2007, Sergei Golovan wrote:
> After some research, we've found that erlang relies on the alignment
> of some global variable. The following patch fixes it:
> --
> --- erlang-11.b.2.orig/erts/emulator/beam/binary.c
On Thu, 25 Jan 2007, Mikael Pettersson wrote:
> Sergei Golovan writes:
> > As one can see, erlang Debian package (R11B-2 relese, 11.b.2 in Debian
> > versioning) fails to build on m68k now
> >
> (http://buildd.debian.org/fetch.cgi?&pkg=erlang&ver=1%3A11.b.2-4&arch=m68k&stamp=1167824208&file=log
On 1/25/07, Mikael Pettersson <[EMAIL PROTECTED]> wrote:
Definitely smells like a toolchain bug to me. In this case, since you've
enabled threads, erts_mtx_t is a properly declared struct type containing
among other things a pthread_mutex_t, an int, and a couple of pointers.
I don't remember how
Sergei Golovan writes:
> Hi!
>
> As one can see, erlang Debian package (R11B-2 relese, 11.b.2 in Debian
> versioning) fails to build on m68k now
> (http://buildd.debian.org/fetch.cgi?&pkg=erlang&ver=1%3A11.b.2-4&arch=m68k&stamp=1167824208&file=log).
>
> After some research, we've found tha
Hi!
As one can see, erlang Debian package (R11B-2 relese, 11.b.2 in Debian
versioning) fails to build on m68k now
(http://buildd.debian.org/fetch.cgi?&pkg=erlang&ver=1%3A11.b.2-4&arch=m68k&stamp=1167824208&file=log).
After some research, we've found that erlang relies on the alignment
of some gl
13 matches
Mail list logo
