From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 58167E00F5A; Tue, 6 Sep 2016 03:49:41 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=5.0 tests=BAYES_00,RDNS_NONE autolearn=no version=3.3.1 X-Spam-HAM-Report: * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 0.8 RDNS_NONE Delivered to internal network by a host with no rDNS Received: from blaine.gmane.org (unknown [195.159.176.226]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 0047EE00CFD for ; Tue, 6 Sep 2016 03:49:36 -0700 (PDT) Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1bhDwa-00018r-Ao for yocto@yoctoproject.org; Tue, 06 Sep 2016 12:49:32 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: yocto@yoctoproject.org From: Pietro Date: Tue, 06 Sep 2016 10:49:44 +0000 Message-ID: <8760q98fqv.fsf@posteo.net> References: <871t0ya6co.fsf@posteo.net> <87fupd8ht2.fsf@posteo.net> Mime-Version: 1.0 X-Complaints-To: usenet@blaine.gmane.org User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4 (gnu/linux) Cancel-Lock: sha1:Cm7Cw+oS/+5mOPFLsIvzA1v2SQE= Subject: Re: arm-*-linux-gnueabi : unrecognized option -Wl, -soname X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Sep 2016 10:49:41 -0000 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Maciej Borzęcki writes: > On Tue, Sep 6, 2016 at 12:05 PM, Pietro wrote: >> >> >> >> "Daniel." writes: >> >>> I *guess* that it should be -Wl,-soname=libgpr.so.1 intead of >>> -Wl,-soname,libgpr.so.1. Now from where this flags are comming is a >>> good question.. >> >> No that is correct, I double checked. >> >> I would love to build the library "by hand" - namely without using >> bitbake - from the build directory, the build log tells : >> >> + bbnote make -j 4 >> CC=arm-phytec-linux-gnueabi-gcc -march=armv7-a -marm -mthumb-interwork >> -mfloat-abi=hard -mfpu=neon -mtune=cortex-a8 >> --sysroot=/export/arm/pietro/PD15.1/build/tmp-glibc/sysroots/phycore-am335x-1 >> LDFLAGS="" >> -I/export/arm/pietro/PD15.1/build/tmp-glibc/work/cortexa8t2hf-vfp-neon-phytec-linux-gnueabi/libgrpc/1.0.0-r0/git/include >> BUILDDIR=/export/arm/pietro/PD15.1/build/tmp-glibc/work/cortexa8t2hf-vfp-neon-phytec-linux-gnueabi/libgrpc/1.0.0-r0/git >> + echo NOTE: make -j 4 CC=arm-phytec-linux-gnueabi-gcc -march=armv7-a >> -marm -mthumb-interwork -mfloat-abi=hard -mfpu=neon -mtune=cortex-a8 >> --sysroot=/export/arm/pietro/PD15.1/build/tmp-glibc/sysroots/phycore-am335x-1 >> LDFLAGS="" >> -I/export/arm/pietro/PD15.1/build/tmp-glibc/work/cortexa8t2hf-vfp-neon-phytec-linux-gnueabi/libgrpc/1.0.0-r0/git/include >> BUILDDIR=/export/arm/pietro/PD15.1/build/tmp-glibc/work/cortexa8t2hf-vfp-neon-phytec-linux-gnueabi/libgrpc/1.0.0-r0/git >> >> Of course jumping in the build directory and issuing the command does >> not work as the make tool does not recognize options such as -marm and >> companions as they are gcc's options. >> >> I have manually added the cross compiler folder to my local PATH but and >> I have quoted all the gcc's options under the CC variable: >> >> >> CC='arm-phytec-linux-gnueabi-gcc -march=armv7-a -marm -mthumb-interwork >> ...' >> >> Is there a standard/better way to do it ? That results in an error as >> some header files could not be found >> >> [C] Compiling src/core/lib/profiling/basic_timers.c >> In file included from >> /export/arm/pietro/PD15.1/build/tmp-glibc/sysroots/phycore-am335x-1/usr/include/features.h:389:0, >> from include/grpc/impl/codegen/port_platform.h:193, >> from >> include/grpc/support/port_platform.h:37, >> from >> src/core/lib/profiling/basic_timers.c:34: >> /export/arm/pietro/PD15.1/build/tmp-glibc/sysroots/phycore-am335x-1/usr/include/gnu/stubs.h:7:29: >> fatal error: >> gnu/stubs-soft.h: No >> such file or >> directory >> # include >> >> I am not getting this error when building using bitbake therefore I am >> pretty sure I am missing some include paths or .. what ? >> > > Maybe the Makefile they have is just not up to the task of cross > compilation. I see that gRPC comes with a cmake setup as well, why not > use that? You'll need `inherit cmake` in your recipe and try with > default build scripts first. > > Cheers, > -- > Maciej Borzecki > RnDity I did try but I am getting errors, cmake results in error when compiling from my machine as well and in fact the gRPC webpage tells CMake is in experimental state: https://github.com/grpc/grpc/blob/master/INSTALL.md