All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pietro <pulsarpietro@posteo.net>
To: yocto@yoctoproject.org
Subject: Re: arm-*-linux-gnueabi : unrecognized option -Wl, -soname
Date: Tue, 06 Sep 2016 10:49:44 +0000	[thread overview]
Message-ID: <8760q98fqv.fsf@posteo.net> (raw)
In-Reply-To: CAD4b0_JXoL7ErkBb9rXh5XWUE4uvqXyDU16yeB=xAMhcq4F0Mg@mail.gmail.com

Maciej Borzęcki
<maciej.borzecki@rndity.com> writes:

> On Tue, Sep 6, 2016 at 12:05 PM, Pietro <pulsarpietro@posteo.net> wrote:
>>
>>
>>
>> "Daniel." <danielhilst@gmail.com> 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 <gnu/stubs-soft.h>
>>
>> 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





      reply	other threads:[~2016-09-06 10:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-05 12:17 arm-*-linux-gnueabi : unrecognized option -Wl, -soname Pietro
2016-09-05 12:44 ` Daniel.
2016-09-05 13:00   ` Pietro
2016-09-05 13:28     ` Daniel.
2016-09-06 17:28     ` Khem Raj
2016-09-06 10:05   ` Pietro
2016-09-06 10:30     ` Maciej Borzęcki
2016-09-06 10:49       ` Pietro [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=8760q98fqv.fsf@posteo.net \
    --to=pulsarpietro@posteo.net \
    --cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.