public inbox for libffi-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Benjamin Lorenz <bl@pocketservices.de>
To: libffi-discuss@sourceware.org
Subject: Re: Compile problem on NetBSD/evbarm
Date: Sun, 25 May 2014 19:59:00 -0000	[thread overview]
Message-ID: <C65114B6-EF03-4DB8-BECA-1320C436D0BF@pocketservices.de> (raw)
In-Reply-To: <D9610876-920F-4BC0-8B7E-5C5FAA810010@pocketservices.de>

Turns out there’s a patch in the pkgsrc package for the arm architecture. When not applying it, using the original code, the assembler is happy. Discussing with the NetBSD maintainers now.

Thanks,
Benjamin


On 25.05.2014, at 16:38, Benjamin Lorenz <bl@pocketservices.de> wrote:

> See below. Please advise. Was trying to compile python2.7 for NetBSD/evbarm.
> 
> Regards,
> Benjamin
> 
> 
> rpi$ uname -a
> NetBSD rpi.pocketservices.de 6.99.41 NetBSD 6.99.41 (RPI) #0: Sat May 17 15:47:42 UTC 2014  builds@b44.netbsd.org:/home/builds/ab/HEAD/evbarm-earmhf/201405171410Z-obj/home/builds/ab/HEAD/src/sys/arch/evbarm/compile/RPI evbarm
> 
> rpi# make
> => Bootstrap dependency digest>=20010302: found digest-20121220
> ===> Building for libffi-3.0.13
> MAKE earmhf-unknown-netbsd6.99.41 :        0 * all
> /usr/bin/make "AR_FLAGS="  "CC_FOR_BUILD="  "CFLAGS=-O2  -Wall -fexceptions"  "CXXFLAGS=-O2"  "CFLAGS_FOR_BUILD="  "CFLAGS_FOR_TARGET="  "INSTALL=/usr/bin/install -c -o root -g wheel"  "INSTALL_DATA=/usr/bin/install -c -o root -g wheel -m 644"  "INSTALL_PROGRAM=/usr/bin/install -c -s -o root -g wheel -m 755"  "INSTALL_SCRIPT=/usr/bin/install -c -o root -g wheel -m 755"  "JC1FLAGS="  "LDFLAGS=-Wl,-R/usr/pkg/lib"  "LIBCFLAGS="  "LIBCFLAGS_FOR_TARGET="  "MAKE=/usr/bin/make"  "MAKEINFO=/usr/pkg/src/devel/libffi/work/.tools/bin/makeinfo "  "PICFLAG="  "PICFLAG_FOR_TARGET="  "RUNTESTFLAGS="  "SHELL=/bin/sh"  "exec_prefix=/usr/pkg"  "infodir=/usr/pkg/info"  "libdir=/usr/pkg/lib"  "mandir=/usr/pkg/man"  "prefix=/usr/pkg"  "AR=ar"  "AS=as"  "CC=gcc"  "CXX=c++"  "LD=/usr/pkg/src/devel/libffi/work/.wrapper/bin/ld"  "NM=/usr/bin/nm -B"  "RANLIB=ranlib"  "DESTDIR=" all-recursive
> Making all in include
> Making all in testsuite
> Making all in man
> depbase=`echo src/arm/sysv.lo | sed 's|[^/]*$|.deps/&|;s|\.lo$||'`; /bin/sh ./libtool    --mode=compile gcc -DHAVE_CONFIG_H -I. -I..   -I. -I../include -Iinclude -I../src  -I. -I../include -Iinclude -I../src -O2 -MT src/arm/sysv.lo -MD -MP -MF $depbase.Tpo -c -o src/arm/sysv.lo ../src/arm/sysv.S && mv -f $depbase.Tpo $depbase.Plo
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I../include -Iinclude -I../src -O2 -MT src/arm/sysv.lo -MD -MP -MF src/arm/.deps/sysv.Tpo -c ../src/arm/sysv.S  -fPIC -DPIC -o src/arm/.libs/sysv.o
> ../src/arm/sysv.S: Assembler messages:
> ../src/arm/sysv.S:227: Error: bad instruction `stmiaeq r2,{r0,r1}'
> ../src/arm/sysv.S:418: Error: bad instruction `stmiaeq r2,{r0,r1}'
> *** Error code 1
> 
> Stop.
> make[3]: stopped in /usr/pkg/src/devel/libffi/work/libffi-3.0.13/arm--netbsdelf
> *** Error code 1


      reply	other threads:[~2014-05-25 19:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6F55A2A6-4264-44F7-8DEB-2BA89D16DD66@pocketservices.de>
2014-05-25 14:38 ` Benjamin Lorenz
2014-05-25 19:59   ` Benjamin Lorenz [this message]

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=C65114B6-EF03-4DB8-BECA-1320C436D0BF@pocketservices.de \
    --to=bl@pocketservices.de \
    --cc=libffi-discuss@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).