From owner-freebsd-arm@freebsd.org Fri Nov 25 16:31:16 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 07BD8C55488 for ; Fri, 25 Nov 2016 16:31:16 +0000 (UTC) (envelope-from punasipuli@t-online.de) Received: from mailout12.t-online.de (mailout12.t-online.de [194.25.134.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mailout00.t-online.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A829DE1E for ; Fri, 25 Nov 2016 16:31:14 +0000 (UTC) (envelope-from punasipuli@t-online.de) Received: from fwd27.aul.t-online.de (fwd27.aul.t-online.de [172.20.26.132]) by mailout12.t-online.de (Postfix) with SMTP id 6B9FD41FCF69 for ; Fri, 25 Nov 2016 17:31:12 +0100 (CET) Received: from [192.168.10.43] (XjAm6kZ-Yh--TQGIiuH8gqpdwr2JUap3K6I2KPrLCJFGJN9-3QArmlfjAwKuc95QNs@[86.56.56.128]) by fwd27.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-SHA encrypted) esmtp id 1cAJP2-0bGfy40; Fri, 25 Nov 2016 17:31:08 +0100 Subject: Re: Rapsberry pi B & VirtualBox crosscompile References: To: freebsd-arm@freebsd.org From: diffusae Message-ID: <8f1fee66-7521-1053-0cac-5a3c70a2c9ec@t-online.de> Date: Fri, 25 Nov 2016 17:31:07 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-ID: XjAm6kZ-Yh--TQGIiuH8gqpdwr2JUap3K6I2KPrLCJFGJN9-3QArmlfjAwKuc95QNs X-TOI-MSGID: d502b3f1-ded0-4eeb-a8be-3d959472bfcb X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Nov 2016 16:31:16 -0000 Hi! I've tried to build a local pkg repository with poudriere and qemu-arm-static on amd64 for armv6 32bit (RPI-B). I am using FreeBSD 11.0-STABLE on both architectures. The build system runs in a VirtualBox environment. For the most packages it works well and with the native-xtools it's also quite fast. But there are some package which won't be build anyway. Unfortunately with package dependencies I like to build. For now, I've recognized it for the following packages: m4, ruby22 and gcc, which has a memory exhausted error, the other packages hang on configure (qemu-arm-static conftest) on different checks: lang/gcc (process:87381): GLib-ERROR (recursed) **: gmem.c:166: failed to allocate 32 bytes{standard input}: Assembler messages: This looks like a problem to build 32bit binaries on 64bit architecture, but I am not sure. devel/m4 checking for working C stack overflow detection... yes lang/ruby22 checking for broken backtrace... make: Working in: /usr/ports/lang/ruby22 I can manually skip the the tests, if I modify the configure script and the packages will be build. Also, if use gcc to compile ruby22 (USE_GCC?= yes) the package will be build. But I don't know how set a variable in make.conf or Makefile to disable the specific configure checks, so poudriere will run automatically with it. I am not sure, if my setup is correct. Thanks a lot Regards, On 15.11.2016 03:39, Mark Millard wrote: > > On 2016-Nov-14, at 5:19 PM, peter garshtja wrote: > >> Hi Krzysztof, >> >> If you want to build packages for your arm system on x86 arch then check it >> here https://github.com/PetruGarstea/FreePI/wiki/Building-FreePI-packages >> >> However freebsd 11 unofficial supports arm pkg repository. >> >> Regards, >> Peter >> >> On Nov 14, 2016 19:25, "Krzysztof Kowalski" wrote: >> >>> Hello there, >>> In few days I will get my 'brand new' RPi B. I would like to have on it >>> FreeBSD 10.3-RELEASE and build ports on it. But as we know, it has low >>> processor power so best way to bulid packages is to use distcc. >>> My question is; >>> Will it works, if I'll use FreeBSD 10.3-RELEASE x84_64, started in >>> VirtualBox with few CPU, to distcc with RPi? I mention that RPi & VB will >>> be connected by crossover ethernet (no switch and only WiFi router at the >>> house where I'll configure RPi). >>> Thanks in advance, best regards, >>> Krzysztof > > One gotcha to using the pkg repository for those that buildworld themselves with > options like -mcpu= (such as -mcpu=corex-a7 for an RPI2B <= V1.1) is that the > software support for instructions that are missing in armv6 but present on the > specific processor/architecture are not always put in place by buildworld. > > This leads to some pure armv6 software (such as from the pkg repository) failing > for lack of routines in the more specialized buildworld context: Undefined symbols > that a just-armv6 buildworld would define. > > If the policy were for buildworld to build the routines despite instructions being > available for the -mcpu= or other more specific context specified for buildworld > then more pkg's from the repository might work for the more targeted buildworld's. > > As I remember pkg itself can have this issue for -mcpu= and the like. But in that > case pkg-static should work fine because it does not depend on the buildworld > libraries for such routines: they are already built in. > > Overall this is somewhat related to the likes of lang/gcc6 based compiles targeting > just armv6 needing -rpath use to avoid failing for things that are "internal > support" (even for arithmetic), like: > > /usr/local/lib/gcc6/libstdc++.so.6: Undefined symbol "__aeabi_uldivmod" > > where /lib/libgcc_s.so.1 does not implement the routine (depending on how buildworld > was done?) but /usr/local/lib/gcc6/libgcc_s.so.1 does implement. > > === > Mark Millard > markmi at dsl-only.net > > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" >