* arm-*-linux-gnueabi : unrecognized option -Wl, -soname
@ 2016-09-05 12:17 Pietro
2016-09-05 12:44 ` Daniel.
0 siblings, 1 reply; 8+ messages in thread
From: Pietro @ 2016-09-05 12:17 UTC (permalink / raw)
To: yocto
Hi all,
I want to cross compile the gRPC library for ARM and I am using the
Yocto build system.
The build fails for the following error, which I am suspicious has
something to do with the compiler being used:
[LD] Linking
/export/arm/xxx/PD15.1/build/tmp-glibc/work/cortexa8t2hf-vfp-neon-phytec-linux-gnueabi/libgrpc/1.0.0-r0/git/libs/opt/libgpr.so.1.0.0-pre1
arm-phytec-linux-gnueabi-ld
: unrecognized option '
-Wl,-soname,libgpr.so.1
arm-phytec-linux-gnueabi-ld
: use the --help option for usage information
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: arm-*-linux-gnueabi : unrecognized option -Wl, -soname
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-06 10:05 ` Pietro
0 siblings, 2 replies; 8+ messages in thread
From: Daniel. @ 2016-09-05 12:44 UTC (permalink / raw)
To: Pietro; +Cc: yocto@yoctoproject.org
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..
2016-09-05 9:17 GMT-03:00 Pietro <pulsarpietro@posteo.net>:
>
> Hi all,
>
> I want to cross compile the gRPC library for ARM and I am using the
> Yocto build system.
>
> The build fails for the following error, which I am suspicious has
> something to do with the compiler being used:
>
>
> [LD] Linking
> /export/arm/xxx/PD15.1/build/tmp-glibc/work/cortexa8t2hf-vfp-neon-phytec-linux-gnueabi/libgrpc/1.0.0-r0/git/libs/opt/libgpr.so.1.0.0-pre1
>
> arm-phytec-linux-gnueabi-ld
> : unrecognized option '
> -Wl,-soname,libgpr.so.1
>
>
> arm-phytec-linux-gnueabi-ld
> : use the --help option for usage information
>
>
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
--
"Do or do not. There is no try"
Yoda Master
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: arm-*-linux-gnueabi : unrecognized option -Wl, -soname
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
1 sibling, 2 replies; 8+ messages in thread
From: Pietro @ 2016-09-05 13:00 UTC (permalink / raw)
To: yocto
Well,
I am cross-compiling the gRPC using the Yocto build system, I have
created a recipe for a new package which generates the gRPC
library(ies).
The error comes from here *guess* :
ifeq ($(SYSTEM),Darwin)
$(Q) $(LD) $(LDFLAGS) -L$(LIBDIR)/$(CONFIG) -install_name
$(SHARED_PREFIX)gpr$(SHARED_VERSION).$(SHARED_EXT) -dynamiclib -o
$(LIBDIR)/$(CONFIG)/libgpr$(SHARED_VERSION).$(SHARED_EXT)
$(LIBGPR_OBJS) $(LDLIBS) $(ZLIB_MERGE_LIBS)
else
$(Q) $(LD) $(LDFLAGS) -L$(LIBDIR)/$(CONFIG) -shared
-Wl,-soname,libgpr.so.1 -o
$(LIBDIR)/$(CONFIG)/libgpr$(SHARED_VERSION).$(SHARED_EXT)
$(LIBGPR_OBJS) $(LDLIBS) $(ZLIB_MERGE_LIBS)
$(Q) ln -sf
$(SHARED_PREFIX)gpr$(SHARED_VERSION).$(SHARED_EXT)
$(LIBDIR)/$(CONFIG)/libgpr$(SHARED_VERSION).so.1
$(Q) ln -sf
$(SHARED_PREFIX)gpr$(SHARED_VERSION).$(SHARED_EXT)
$(LIBDIR)/$(CONFIG)/libgpr$(SHARED_VERSION).so
endif
What's puzzles me is that the same source code builds without problem on
my machine (not cross compiled).
It might be a question for gRPC developers though
"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..
>
> 2016-09-05 9:17 GMT-03:00 Pietro <pulsarpietro@posteo.net>:
>>
>> Hi all,
>>
>> I want to cross compile the gRPC library for ARM and I am using the
>> Yocto build system.
>>
>> The build fails for the following error, which I am suspicious has
>> something to do with the compiler being used:
>>
>>
>> [LD] Linking
>> /export/arm/xxx/PD15.1/build/tmp-glibc/work/cortexa8t2hf-vfp-neon-phytec-linux-gnueabi/libgrpc/1.0.0-r0/git/libs/opt/libgpr.so.1.0.0-pre1
>>
>> arm-phytec-linux-gnueabi-ld
>> : unrecognized option '
>> -Wl,-soname,libgpr.so.1
>>
>>
>> arm-phytec-linux-gnueabi-ld
>> : use the --help option for usage information
>>
>>
>> --
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>
>
>
> --
> "Do or do not. There is no try"
> Yoda Master
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: arm-*-linux-gnueabi : unrecognized option -Wl, -soname
2016-09-05 13:00 ` Pietro
@ 2016-09-05 13:28 ` Daniel.
2016-09-06 17:28 ` Khem Raj
1 sibling, 0 replies; 8+ messages in thread
From: Daniel. @ 2016-09-05 13:28 UTC (permalink / raw)
To: Pietro; +Cc: yocto@yoctoproject.org
Try to crosscompile "by hand" using Yocto toolschains. then try to
crosscompile it inside Yocto. Does gRPC uses autotools? If so you may
be interested in $CONFIGURE_FLAGS setted by Yocto' environment setup
script. Here is an example of how I did compile libfprint using
Yocto's toolchain: http://pastebin.com/hyzrd3up
Regards :)
2016-09-05 10:00 GMT-03:00 Pietro <pulsarpietro@posteo.net>:
> Well,
>
> I am cross-compiling the gRPC using the Yocto build system, I have
> created a recipe for a new package which generates the gRPC
> library(ies).
>
> The error comes from here *guess* :
> ifeq ($(SYSTEM),Darwin)
> $(Q) $(LD) $(LDFLAGS) -L$(LIBDIR)/$(CONFIG) -install_name
> $(SHARED_PREFIX)gpr$(SHARED_VERSION).$(SHARED_EXT) -dynamiclib -o
> $(LIBDIR)/$(CONFIG)/libgpr$(SHARED_VERSION).$(SHARED_EXT)
> $(LIBGPR_OBJS) $(LDLIBS) $(ZLIB_MERGE_LIBS)
> else
> $(Q) $(LD) $(LDFLAGS) -L$(LIBDIR)/$(CONFIG) -shared
> -Wl,-soname,libgpr.so.1 -o
> $(LIBDIR)/$(CONFIG)/libgpr$(SHARED_VERSION).$(SHARED_EXT)
> $(LIBGPR_OBJS) $(LDLIBS) $(ZLIB_MERGE_LIBS)
> $(Q) ln -sf
> $(SHARED_PREFIX)gpr$(SHARED_VERSION).$(SHARED_EXT)
> $(LIBDIR)/$(CONFIG)/libgpr$(SHARED_VERSION).so.1
> $(Q) ln -sf
> $(SHARED_PREFIX)gpr$(SHARED_VERSION).$(SHARED_EXT)
> $(LIBDIR)/$(CONFIG)/libgpr$(SHARED_VERSION).so
> endif
>
> What's puzzles me is that the same source code builds without problem on
> my machine (not cross compiled).
>
> It might be a question for gRPC developers though
>
> "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..
>>
>> 2016-09-05 9:17 GMT-03:00 Pietro <pulsarpietro@posteo.net>:
>>>
>>> Hi all,
>>>
>>> I want to cross compile the gRPC library for ARM and I am using the
>>> Yocto build system.
>>>
>>> The build fails for the following error, which I am suspicious has
>>> something to do with the compiler being used:
>>>
>>>
>>> [LD] Linking
>>> /export/arm/xxx/PD15.1/build/tmp-glibc/work/cortexa8t2hf-vfp-neon-phytec-linux-gnueabi/libgrpc/1.0.0-r0/git/libs/opt/libgpr.so.1.0.0-pre1
>>>
>>> arm-phytec-linux-gnueabi-ld
>>> : unrecognized option '
>>> -Wl,-soname,libgpr.so.1
>>>
>>>
>>> arm-phytec-linux-gnueabi-ld
>>> : use the --help option for usage information
>>>
>>>
>>> --
>>> _______________________________________________
>>> yocto mailing list
>>> yocto@yoctoproject.org
>>> https://lists.yoctoproject.org/listinfo/yocto
>>
>>
>>
>> --
>> "Do or do not. There is no try"
>> Yoda Master
>
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
--
"Do or do not. There is no try"
Yoda Master
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: arm-*-linux-gnueabi : unrecognized option -Wl, -soname
2016-09-05 13:00 ` Pietro
2016-09-05 13:28 ` Daniel.
@ 2016-09-06 17:28 ` Khem Raj
1 sibling, 0 replies; 8+ messages in thread
From: Khem Raj @ 2016-09-06 17:28 UTC (permalink / raw)
To: Pietro; +Cc: yocto
[-- Attachment #1: Type: text/plain, Size: 2935 bytes --]
> On Sep 5, 2016, at 6:00 AM, Pietro <pulsarpietro@posteo.net> wrote:
>
> Well,
>
> I am cross-compiling the gRPC using the Yocto build system, I have
> created a recipe for a new package which generates the gRPC
> library(ies).
>
> The error comes from here *guess* :
> ifeq ($(SYSTEM),Darwin)
> $(Q) $(LD) $(LDFLAGS) -L$(LIBDIR)/$(CONFIG) -install_name
> $(SHARED_PREFIX)gpr$(SHARED_VERSION).$(SHARED_EXT) -dynamiclib -o
> $(LIBDIR)/$(CONFIG)/libgpr$(SHARED_VERSION).$(SHARED_EXT)
> $(LIBGPR_OBJS) $(LDLIBS) $(ZLIB_MERGE_LIBS)
> else
> $(Q) $(LD) $(LDFLAGS) -L$(LIBDIR)/$(CONFIG) -shared
> -Wl,-soname,libgpr.so.1 -o
> $(LIBDIR)/$(CONFIG)/libgpr$(SHARED_VERSION).$(SHARED_EXT)
> $(LIBGPR_OBJS) $(LDLIBS) $(ZLIB_MERGE_LIBS)
> $(Q) ln -sf
> $(SHARED_PREFIX)gpr$(SHARED_VERSION).$(SHARED_EXT)
> $(LIBDIR)/$(CONFIG)/libgpr$(SHARED_VERSION).so.1
> $(Q) ln -sf
> $(SHARED_PREFIX)gpr$(SHARED_VERSION).$(SHARED_EXT)
> $(LIBDIR)/$(CONFIG)/libgpr$(SHARED_VERSION).so
> endif
>
> What's puzzles me is that the same source code builds without problem on
> my machine (not cross compiled).
>
> It might be a question for gRPC developers though
that option -Wl,-soname,xxxx assumes LD = “gcc driver”
however when using OE, that may not be case LD variable may point to
bare ld. So in your recipe you should take care of the assumption
your makefile is making and set LD = CC
>
> "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..
>>
>> 2016-09-05 9:17 GMT-03:00 Pietro <pulsarpietro@posteo.net>:
>>>
>>> Hi all,
>>>
>>> I want to cross compile the gRPC library for ARM and I am using the
>>> Yocto build system.
>>>
>>> The build fails for the following error, which I am suspicious has
>>> something to do with the compiler being used:
>>>
>>>
>>> [LD] Linking
>>> /export/arm/xxx/PD15.1/build/tmp-glibc/work/cortexa8t2hf-vfp-neon-phytec-linux-gnueabi/libgrpc/1.0.0-r0/git/libs/opt/libgpr.so.1.0.0-pre1
>>>
>>> arm-phytec-linux-gnueabi-ld
>>> : unrecognized option '
>>> -Wl,-soname,libgpr.so.1
>>>
>>>
>>> arm-phytec-linux-gnueabi-ld
>>> : use the --help option for usage information
>>>
>>>
>>> --
>>> _______________________________________________
>>> yocto mailing list
>>> yocto@yoctoproject.org
>>> https://lists.yoctoproject.org/listinfo/yocto
>>
>>
>>
>> --
>> "Do or do not. There is no try"
>> Yoda Master
>
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 211 bytes --]
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: arm-*-linux-gnueabi : unrecognized option -Wl, -soname
2016-09-05 12:44 ` Daniel.
2016-09-05 13:00 ` Pietro
@ 2016-09-06 10:05 ` Pietro
2016-09-06 10:30 ` Maciej Borzęcki
1 sibling, 1 reply; 8+ messages in thread
From: Pietro @ 2016-09-06 10:05 UTC (permalink / raw)
To: yocto
"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 ?
>
> 2016-09-05 9:17 GMT-03:00 Pietro <pulsarpietro@posteo.net>:
>>
>> Hi all,
>>
>> I want to cross compile the gRPC library for ARM and I am using the
>> Yocto build system.
>>
>> The build fails for the following error, which I am suspicious has
>> something to do with the compiler being used:
>>
>>
>> [LD] Linking
>> /export/arm/xxx/PD15.1/build/tmp-glibc/work/cortexa8t2hf-vfp-neon-phytec-linux-gnueabi/libgrpc/1.0.0-r0/git/libs/opt/libgpr.so.1.0.0-pre1
>>
>> arm-phytec-linux-gnueabi-ld
>> : unrecognized option '
>> -Wl,-soname,libgpr.so.1
>>
>>
>> arm-phytec-linux-gnueabi-ld
>> : use the --help option for usage information
>>
>>
>> --
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>
>
>
> --
> "Do or do not. There is no try"
> Yoda Master
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: arm-*-linux-gnueabi : unrecognized option -Wl, -soname
2016-09-06 10:05 ` Pietro
@ 2016-09-06 10:30 ` Maciej Borzęcki
2016-09-06 10:49 ` Pietro
0 siblings, 1 reply; 8+ messages in thread
From: Maciej Borzęcki @ 2016-09-06 10:30 UTC (permalink / raw)
To: Pietro; +Cc: yocto
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
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: arm-*-linux-gnueabi : unrecognized option -Wl, -soname
2016-09-06 10:30 ` Maciej Borzęcki
@ 2016-09-06 10:49 ` Pietro
0 siblings, 0 replies; 8+ messages in thread
From: Pietro @ 2016-09-06 10:49 UTC (permalink / raw)
To: yocto
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
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2016-09-06 17:28 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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.