Re: [yocto] LLVM: error adding symbols: File in wrong format

[Giordon Stark]

I see this error
in 
/local/d6/gstark/poky/build/tmp/work/aarch64-poky-linux/root/6.14.00-r0/temp/log.do_compile.21706:

/local/d6/gstark/poky/build/tmp/work/aarch64-poky-linux/root/6.14.00-r0/recipe-sysroot-native/usr/lib/libLLVMSupport.a:
error adding symbols: File in wrong format
clang-5.0: ^[[0;1;31merror: ^[[0mlinker command failed with exit code 1
(use -v to see invocation)^[[0m
interpreter/llvm/src/tools/clang/utils/TableGen/CMakeFiles/clang-tblgen.dir/build.make:95:
recipe for target 'interpreter/llvm/src/bin/clang-tblgen' failed
make[2]: *** [interpreter/llvm/src/bin/clang-tblgen] Error 1
make[2]: Leaving directory
'/local/d6/gstark/poky/build/tmp/work/aarch64-poky-linux/root/6.14.00-r0/build'
CMakeFiles/Makefile2:791: recipe for target
'interpreter/llvm/src/tools/clang/utils/TableGen/CMakeFiles/clang-tblgen.dir/all'
failed
make[1]: ***
[interpreter/llvm/src/tools/clang/utils/TableGen/CMakeFiles/clang-tblgen.dir/all]
Error 2
make[1]: *** Waiting for unfinished jobs

Looking at the CMakeError.log
(/local/d6/gstark/poky/build/tmp/work/aarch64-poky-linux/root/6.14.00-r0/build/CMakeFiles/CMakeError.log),
it seems I'm missing some extra links to pthread, perhaps?

/usr/src/debug/root/6.14.00-r0/build/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8:
undefined reference to `pthread_create'
/usr/src/debug/root/6.14.00-r0/build/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8:
undefined reference to `pthread_create'

I've gisted the CMakeError.log file here:
https://gist.github.com/4fb229e696659c3a905fa090e67e2d02

Giordon

On Fri, Jul 13, 2018 at 10:36 AM Giordon Stark  wrote:

> Hi Khem,
>
> For meta-clang -- I'm on rocko. Is that truly too old? I'm going to switch
> to sumo in the next few weeks, but I was hoping to nail some of these
> recipes before I switch to sumo (one of the bigger things is the update to
> the linux kernel when switching will give me a bunch of patches for QSPI
> for the machines I'm on and I need to debug the QSPI first before switching
> over...)
>
> commit a4c0cd28de9c3d5823be43150a76d221b08896d6
> Author: Khem Raj 
> Date:   Tue Dec 12 19:02:54 2017 -0800
>
> clang: Update to latest on release_50
>
> Fixes issue #47
>
> Signed-off-by: Khem Raj 
>
> and I think I have the particular commit you're linking:
>
> kratsg@dc:~/d4/gstark/meta-clang$ git branch --contains e9def8f1
>   master
> * rocko
>
> So I will go ahead and add the extra TUNES you listed at the end of your
> email and see if that works for me.
>
> Giordon
>
> On Fri, Jul 13, 2018 at 10:32 AM Khem Raj  wrote:
>
>> Hi Giordon
>>
>> I realised that you are on an older release can you cherry pick
>>
>> https://github.com/kraj/meta-clang/commit/e9def8f1
>>
>> I hope that will be helpful this was done for armv7ve/rpi3
>>
>> I think that you need to add following for your case. If it works you
>> can send the patches for the branch you are on.
>>
>> TUNE_CCARGS_remove_toolchain-clang = "-march=armv7-a"
>> TUNE_CCARGS_append_toolchain-clang =
>> "${@bb.utils.contains("TUNE_FEATURES", "armv7a", " -march=armv7a", "",
>> d)}"
>> On Fri, Jul 13, 2018 at 8:00 AM Giordon Stark  wrote:
>> >
>> > Hi Khem,
>> >
>> > I've uploaded the gist here:
>> https://gist.github.com/ef8b964d563b9b0c5249b199033d7b6e
>> >
>> > Looks like the error is:
>> >
>> > clang-5.0: error: the clang compiler does not support '-march=armv7-a'
>> >
>> > Giordon
>> >
>> > On Fri, Jul 13, 2018 at 1:30 AM Khem Raj  wrote:
>> >>
>> >> Hi Giordon
>> >>
>> >> I think there is something else going on. Can you check
>> >>
>> /local/d4/gstark/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/root/6.14.00-r0/build/CMakeFiles/CMakeError.log
>> >>
>> >> and see what error message is being spit out by clang when its trying
>> >> to compile the sample file to detect c++11
>> >> On Thu, Jul 12, 2018 at 1:57 PM Giordon Stark 
>> wrote:
>> >> >
>> >> > Hi Khem,
>> >> >
>> >> > I added clang, removed llvm-native -- and now I get an llvm error --
>> supposedly because the llvm being used with yocto may be too old(?).
>> >> >
>> >> > kratsg@dc:/local/d4/gstark/poky/build$ bitbake root
>> >> > Loading cache: 100%
>> ||
>> Time: 0:00:00
>> >> > Loaded 3854 entries from dependency 

Re: [yocto] Writing a recipe that allows for extra depends, depending on the extra_oemake configurations

[Giordon Stark]

Thanks all! I did mean OE_CMAKE [I'm not the best typer].

Giordon

On Fri, Jul 13, 2018 at 2:53 AM Burton, Ross  wrote:

> On 12 July 2018 at 23:12, Giordon Stark  wrote:
> > Hi Ross,
> >
> > Thanks. I saw that but the documentation doesn't explicitly mentioned
> > EXTRA_OEMAKE. Is that the same as EXTRA_OECONF?
>
> EXTRA_OEMAKE is what is passed to 'make' calls.  Your recipe is using
> cmake, so you're extending EXTRA_OECMAKE, which is passed to cmake
> calls.
>
> If you read the documentation you'll see that PACKAGECONFIG is parsed
> and the appropriate enabled/disabled options are added to
> PACKAGECONFIG_CONFARGS, which cmake.bbclass adds to EXTRA_OECMAKE for
> you.
>
> Ross
>
-- 
Giordon Stark
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] LLVM: error adding symbols: File in wrong format

[Giordon Stark]

Hi Khem,

For meta-clang -- I'm on rocko. Is that truly too old? I'm going to switch
to sumo in the next few weeks, but I was hoping to nail some of these
recipes before I switch to sumo (one of the bigger things is the update to
the linux kernel when switching will give me a bunch of patches for QSPI
for the machines I'm on and I need to debug the QSPI first before switching
over...)

commit a4c0cd28de9c3d5823be43150a76d221b08896d6
Author: Khem Raj 
Date:   Tue Dec 12 19:02:54 2017 -0800

clang: Update to latest on release_50

Fixes issue #47

Signed-off-by: Khem Raj 

and I think I have the particular commit you're linking:

kratsg@dc:~/d4/gstark/meta-clang$ git branch --contains e9def8f1
  master
* rocko

So I will go ahead and add the extra TUNES you listed at the end of your
email and see if that works for me.

Giordon

On Fri, Jul 13, 2018 at 10:32 AM Khem Raj  wrote:

> Hi Giordon
>
> I realised that you are on an older release can you cherry pick
>
> https://github.com/kraj/meta-clang/commit/e9def8f1
>
> I hope that will be helpful this was done for armv7ve/rpi3
>
> I think that you need to add following for your case. If it works you
> can send the patches for the branch you are on.
>
> TUNE_CCARGS_remove_toolchain-clang = "-march=armv7-a"
> TUNE_CCARGS_append_toolchain-clang =
> "${@bb.utils.contains("TUNE_FEATURES", "armv7a", " -march=armv7a", "",
> d)}"
> On Fri, Jul 13, 2018 at 8:00 AM Giordon Stark  wrote:
> >
> > Hi Khem,
> >
> > I've uploaded the gist here:
> https://gist.github.com/ef8b964d563b9b0c5249b199033d7b6e
> >
> > Looks like the error is:
> >
> > clang-5.0: error: the clang compiler does not support '-march=armv7-a'
> >
> > Giordon
> >
> > On Fri, Jul 13, 2018 at 1:30 AM Khem Raj  wrote:
> >>
> >> Hi Giordon
> >>
> >> I think there is something else going on. Can you check
> >>
> /local/d4/gstark/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/root/6.14.00-r0/build/CMakeFiles/CMakeError.log
> >>
> >> and see what error message is being spit out by clang when its trying
> >> to compile the sample file to detect c++11
> >> On Thu, Jul 12, 2018 at 1:57 PM Giordon Stark  wrote:
> >> >
> >> > Hi Khem,
> >> >
> >> > I added clang, removed llvm-native -- and now I get an llvm error --
> supposedly because the llvm being used with yocto may be too old(?).
> >> >
> >> > kratsg@dc:/local/d4/gstark/poky/build$ bitbake root
> >> > Loading cache: 100%
> ||
> Time: 0:00:00
> >> > Loaded 3854 entries from dependency cache.
> >> > Parsing recipes: 100%
> |##|
> Time: 0:00:03
> >> > Parsing of 2600 .bb files complete (2598 cached, 2 parsed). 3853
> targets, 163 skipped, 0 masked, 0 errors.
> >> > NOTE: Resolving any missing task queue dependencies
> >> >
> >> > Build Configuration:
> >> > BB_VERSION   = "1.36.0"
> >> > BUILD_SYS= "x86_64-linux"
> >> > NATIVELSBSTRING  = "universal"
> >> > TARGET_SYS   = "arm-poky-linux-gnueabi"
> >> > MACHINE  = "zc702-zynq7"
> >> > DISTRO   = "poky"
> >> > DISTRO_VERSION   = "2.4.2"
> >> > TUNE_FEATURES= "arm armv7a vfp thumb neon callconvention-hard
> cortexa9"
> >> > TARGET_FPU   = "hard"
> >> > meta
> >> > meta-poky
> >> > meta-yocto-bsp   =
> "rocko:cca8bde9d700d68c5f36d7d4c47c048526aedfc0"
> >> > meta-xilinx-bsp  =
> "rocko:7935ef724cd7359ed97e6ae3d90ebc8f07dd7e1f"
> >> > meta-oe
> >> > meta-python  =
> "rocko:dacfa2b1920e285531bec55cd2f08743390aaf57"
> >> > meta =
> "rocko:7dccdf82d49fb11cb2a7cb205ae08311e5d43291"
> >> > meta-clang   =
> "rocko:a4c0cd28de9c3d5823be43150a76d221b08896d6"
> >> > meta-l1calo  =
> "update/ROOT:0cfb5bfd77ec9bb9fb9afbf4271786842a5dff8f"
> >> > workspace=
> "rocko:cca8bde9d700d68c5f36d7d4c47c048526aedfc0"
>

Re: [yocto] LLVM: error adding symbols: File in wrong format

[Giordon Stark]

Hi Khem,

I've uploaded the gist here:
https://gist.github.com/ef8b964d563b9b0c5249b199033d7b6e

Looks like the error is:

clang-5.0: error: the clang compiler does not support '-march=armv7-a'

Giordon

On Fri, Jul 13, 2018 at 1:30 AM Khem Raj  wrote:

> Hi Giordon
>
> I think there is something else going on. Can you check
>
> /local/d4/gstark/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/root/6.14.00-r0/build/CMakeFiles/CMakeError.log
>
> and see what error message is being spit out by clang when its trying
> to compile the sample file to detect c++11
> On Thu, Jul 12, 2018 at 1:57 PM Giordon Stark  wrote:
> >
> > Hi Khem,
> >
> > I added clang, removed llvm-native -- and now I get an llvm error --
> supposedly because the llvm being used with yocto may be too old(?).
> >
> > kratsg@dc:/local/d4/gstark/poky/build$ bitbake root
> > Loading cache: 100%
> ||
> Time: 0:00:00
> > Loaded 3854 entries from dependency cache.
> > Parsing recipes: 100%
> |##|
> Time: 0:00:03
> > Parsing of 2600 .bb files complete (2598 cached, 2 parsed). 3853
> targets, 163 skipped, 0 masked, 0 errors.
> > NOTE: Resolving any missing task queue dependencies
> >
> > Build Configuration:
> > BB_VERSION   = "1.36.0"
> > BUILD_SYS= "x86_64-linux"
> > NATIVELSBSTRING  = "universal"
> > TARGET_SYS   = "arm-poky-linux-gnueabi"
> > MACHINE  = "zc702-zynq7"
> > DISTRO   = "poky"
> > DISTRO_VERSION   = "2.4.2"
> > TUNE_FEATURES= "arm armv7a vfp thumb neon callconvention-hard
> cortexa9"
> > TARGET_FPU   = "hard"
> > meta
> > meta-poky
> > meta-yocto-bsp   = "rocko:cca8bde9d700d68c5f36d7d4c47c048526aedfc0"
> > meta-xilinx-bsp  = "rocko:7935ef724cd7359ed97e6ae3d90ebc8f07dd7e1f"
> > meta-oe
> > meta-python  = "rocko:dacfa2b1920e285531bec55cd2f08743390aaf57"
> > meta = "rocko:7dccdf82d49fb11cb2a7cb205ae08311e5d43291"
> > meta-clang   = "rocko:a4c0cd28de9c3d5823be43150a76d221b08896d6"
> > meta-l1calo  =
> "update/ROOT:0cfb5bfd77ec9bb9fb9afbf4271786842a5dff8f"
> > workspace= "rocko:cca8bde9d700d68c5f36d7d4c47c048526aedfc0"
> >
> > Initialising tasks: 100%
> |###|
> Time: 0:00:03
> > NOTE: Executing SetScene Tasks
> > NOTE: Executing RunQueue Tasks
> > ERROR: root-6.14.00-r0 do_configure: Function failed: do_configure (log
> file is located at
> /local/d4/gstark/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/root/6.14.00-r0/temp/log.do_configure.2984)
> > ERROR: Logfile of failure stored in:
> /local/d4/gstark/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/root/6.14.00-r0/temp/log.do_configure.2984
> > Log data follows:
> > | DEBUG: Executing shell function do_configure
> > | -- The C compiler identification is Clang 5.0.1
> > | -- The CXX compiler identification is Clang 5.0.1
> > | -- Check for working C compiler:
> /local/d4/gstark/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/root/6.14.00-r0/recipe-sysroot-native/usr/bin/arm-poky-linux-gnueabi/arm-poky-linux-gnueabi-clang
> > | -- Check for working C compiler:
> /local/d4/gstark/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/root/6.14.00-r0/recipe-sysroot-native/usr/bin/arm-poky-linux-gnueabi/arm-poky-linux-gnueabi-clang
> -- works
> > | -- Detecting C compiler ABI info
> > | -- Detecting C compiler ABI info - done
> > | -- Detecting C compile features
> > | -- Detecting C compile features - done
> > | -- Check for working CXX compiler:
> /local/d4/gstark/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/root/6.14.00-r0/recipe-sysroot-native/usr/bin/arm-poky-linux-gnueabi/arm-poky-linux-gnueabi-clang++
> > | -- Check for working CXX compiler:
> /local/d4/gstark/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/root/6.14.00-r0/recipe-sysroot-native/usr/bin/arm-poky-linux-gnueabi/arm-poky-linux-gnueabi-clang++
> -- works
> > | -- Detecting CXX compiler ABI info
> > | -- Dete

Re: [yocto] Writing a recipe that allows for extra depends, depending on the extra_oemake configurations

[Giordon Stark]

Hi Ross,

Thanks. I saw that but the documentation doesn't explicitly mentioned
EXTRA_OEMAKE. Is that the same as EXTRA_OECONF?

Giordon

On Thu, Jul 12, 2018 at 5:08 PM Burton, Ross  wrote:

> > I'm wondering how I can make it so that I can have a user allow for
> > additional configuration to enable crypto/krb5 which requires extra
> depends
> > and changing the oemake flags. Is this something Yocto can do, or is it
> > better to have users provide a bbappend file to update this recipe?
>
> Yes, PACKAGECONFIG is exactly what you want.
>
>
> https://www.yoctoproject.org/docs/2.4.2/ref-manual/ref-manual.html#var-PACKAGECONFIG
>
> Ross
>
-- 
Giordon Stark
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Writing a recipe that allows for extra depends, depending on the extra_oemake configurations

[Giordon Stark]

Hi,

I have a recipe that I wrote up here:
https://github.com/kratsg/meta-l1calo/blob/master/recipes-core/root/xrootd_4.8.3.bb
 .

The short snippet of it looks as follows:

inherit cmake

DEPENDS += "python"

*# ENABLE_CRYPTO*
*#DEPENDS += "openssl"*

*# ENABLE_KRB5*
*#DEPENDS += "krb5"*

EXTRA_OECMAKE = " \
  -DENABLE_PERL=FALSE \
  -DENABLE_FUSE=FALSE \
*  -DENABLE_CRYPTO=FALSE \*
*  -DENABLE_KRB5=FALSE \*
  -DENABLE_FUSE=FALSE \
  -DENABLE_READLINE=FALSE \
  -DHAVE_ATOMICS_EXITCODE=0 \
"

I'm wondering how I can make it so that I can have a user allow for
additional configuration to enable crypto/krb5 which requires extra depends
and changing the oemake flags. Is this something Yocto can do, or is it
better to have users provide a bbappend file to update this recipe?

Thanks,

Giordon
-- 
Giordon Stark
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] LLVM: error adding symbols: File in wrong format

[Giordon Stark]

rk/cortexa9hf-neon-poky-linux-gnueabi/root/6.14.00-r0/recipe-sysroot/usr/include
| -- Davix not found, switching ON 'builtin_davix' option.
| -- Looking for clock_gettime
| -- Looking for clock_gettime - not found
| -- Looking for clock_gettime in rt
| -- Looking for clock_gettime in rt - not found
| -- Looking for TBB
| -- Could NOT find TBB (missing:  TBB_ROOT_DIR TBB_INCLUDE_DIR TBB_LIBRARY)
| -- TBB not found. Switching on builtin_tbb option
| -- Performing Test CXX_HAS_mno_rtm
| -- Performing Test CXX_HAS_mno_rtm - Failed
| -- Looking for BLAS for optional parts of TMVA
| -- A library with BLAS API not found. Please specify library location.
| -- Using GSL CBLAS for optional parts of TMVA
| -- Enabled support for:  builtin_davix builtin_ftgl builtin_gl2ps
builtin_clang builtin_tbb builtin_xxhash cling cxx11 davix exceptions
explicitlink fftw3 gdml genvector http imt mathmore minuit2 opengl pch
python roofit shared sqlite ssl thread tmva tmva-cpu x11 xft xml xrootd
| -- Found LLVM_CONFIG as
/local/d4/gstark/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/root/6.14.00-r0/recipe-sysroot-native/usr/bin/llvm-config
| -- Linker detection: GNU ld
*| CMake Warning at
/local/d4/gstark/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/root/6.14.00-r0/recipe-sysroot-native/usr/lib/cmake/llvm/HandleLLVMOptions.cmake:185
(message):*
*|   -fPIC is not supported.*
*| Call Stack (most recent call first):*
*|
 
/local/d4/gstark/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/root/6.14.00-r0/recipe-sysroot-native/usr/lib/cmake/llvm/HandleLLVMOptions.cmake:213
(add_flag_or_print_warning)*
*|   interpreter/CMakeLists.txt:285 (include)*
*| *
*| *
*| CMake Error at
/local/d4/gstark/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/root/6.14.00-r0/recipe-sysroot-native/usr/lib/cmake/llvm/HandleLLVMOptions.cmake:402
(message):*
*|   LLVM requires C++11 support but the '-std=c++11' flag isn't supported.*
*| Call Stack (most recent call first):*
*|   interpreter/CMakeLists.txt:285 (include)*
*| *
*| *
| -- Configuring incomplete, errors occurred!
| See also
"/local/d4/gstark/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/root/6.14.00-r0/build/CMakeFiles/CMakeOutput.log".
| See also
"/local/d4/gstark/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/root/6.14.00-r0/build/CMakeFiles/CMakeError.log".
| WARNING:
/local/d4/gstark/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/root/6.14.00-r0/temp/run.do_configure.2984:1
exit 1 from 'cmake $oecmake_sitefile
/local/d4/gstark/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/root/6.14.00-r0/root-6.14.00
-DCMAKE_INSTALL_PREFIX:PATH=/usr -DCMAKE_INSTALL_BINDIR:PATH=bin
-DCMAKE_INSTALL_SBINDIR:PATH=sbin -DCMAKE_INSTALL_LIBEXECDIR:PATH=libexec
-DCMAKE_INSTALL_SYSCONFDIR:PATH=/etc
-DCMAKE_INSTALL_SHAREDSTATEDIR:PATH=../com
-DCMAKE_INSTALL_LOCALSTATEDIR:PATH=/var -DCMAKE_INSTALL_LIBDIR:PATH=lib
-DCMAKE_INSTALL_INCLUDEDIR:PATH=include
-DCMAKE_INSTALL_DATAROOTDIR:PATH=share -DCMAKE_INSTALL_SO_NO_EXE=0
-DCMAKE_TOOLCHAIN_FILE=/local/d4/gstark/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/root/6.14.00-r0/toolchain.cmake
-DCMAKE_VERBOSE_MAKEFILE=1 -DCMAKE_NO_SYSTEM_FROM_IMPORTED=1 -Drootfit=ON
-Dminuit2=ON -Dpython=ON -Dssl=ON -Dxrootd=ON -Dbuiltin_freetype=OFF
-Dbuiltin_llvm=OFF -Dbuiltin_glew=OFF -Dastiff=OFF -Dasimage=OFF
-Dbuiltin_afterimage=OFF -Dalien=OFF -Dvdt=OFF ${PACKAGECONFIG_CONFARGS}
-Wno-dev'
| ERROR: Function failed: do_configure (log file is located at
/local/d4/gstark/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/root/6.14.00-r0/temp/log.do_configure.2984)
ERROR: Task 
(/local/d4/gstark/meta-l1calo/recipes-core/root/root_6.14.00.bb:do_configure)
failed with exit code '1'


On Wed, Jul 11, 2018 at 3:35 PM Khem Raj  wrote:

> Hi Giordon
>
> On Tue, Jul 10, 2018 at 10:36 AM Giordon Stark  wrote:
> >
> > Hi all,
> >
> > |
> /local/d4/gstark/poky/build/tmp/work/aarch64-poky-linux/root/6.14.00-r0/recipe-sysroot-native/usr/lib/libLLVMSupport.a:
> error adding symbols: File in wrong format
> > | clang-5.0: error: linker command failed with exit code 1 (use -v to
> see invocation)
> > |
> interpreter/llvm/src/tools/clang/utils/TableGen/CMakeFiles/clang-tblgen.dir/build.make:95:
> recipe for target 'interpreter/llvm/src/bin/clang-tblgen' failed
> > | make[2]: *** [interpreter/llvm/src/bin/clang-tblgen] Error 1
> > | make[2]: Leaving directory
> '/local/d4/gstark/poky/build/tmp/work/aarch64-poky-linux/root/6.14.00-r0/build'
> > | CMakeFiles/Makefile2:791: recipe for target
> 'interpreter/llvm/src/tools/clang/utils/TableGen/CMakeFiles/clang-tblgen.dir/all'
> failed
> > | make[1]: ***
> [interpreter/llvm/src/tools/clang/utils/TableGen/CMakeFiles/clang-tblgen.dir/all]
> Error 2
> > | make[1]: *** Waiting for unfinished jobs
> >
> > Here's the full log:
> https://gist.github.com/3403addf74b5e902ade

[yocto] LLVM: error adding symbols: File in wrong format

[Giordon Stark]

Hi all,

|
/local/d4/gstark/poky/build/tmp/work/aarch64-poky-linux/root/6.14.00-r0/recipe-sysroot-native/usr/lib/libLLVMSupport.a:
error adding symbols: File in wrong format
| clang-5.0: error: linker command failed with exit code 1 (use -v to see
invocation)
|
interpreter/llvm/src/tools/clang/utils/TableGen/CMakeFiles/clang-tblgen.dir/build.make:95:
recipe for target 'interpreter/llvm/src/bin/clang-tblgen' failed
| make[2]: *** [interpreter/llvm/src/bin/clang-tblgen] Error 1
| make[2]: Leaving directory
'/local/d4/gstark/poky/build/tmp/work/aarch64-poky-linux/root/6.14.00-r0/build'
| CMakeFiles/Makefile2:791: recipe for target
'interpreter/llvm/src/tools/clang/utils/TableGen/CMakeFiles/clang-tblgen.dir/all'
failed
| make[1]: ***
[interpreter/llvm/src/tools/clang/utils/TableGen/CMakeFiles/clang-tblgen.dir/all]
Error 2
| make[1]: *** Waiting for unfinished jobs

Here's the full log:
https://gist.github.com/3403addf74b5e902adec93b75fb0e138

Any ideas how to get a more verbose invocation if needed? I suspect the
error is due to some pre-built libraries being shipped in this recipe, but
I'm not sure what's causing the error in the first place.

Note: I am using meta-clang. The recipe I'm using looks like:

SUMMARY = "Numerical data analysis framework (OO)"
DESCRIPTION = "Object oriented framework for large scale data analysis"
HOMEPAGE = "http://root.cern.ch;
LICENSE = "LGPLv2.1"
LIC_FILES_CHKSUM = "file://LICENSE;md5=5ec773ab82cbea1f17ec5b98e8ce60cf"
SRC_URI = "https://root.cern.ch/download/root_v${PV}.source.tar.gz;

S = "${WORKDIR}/${BPN}-${PV}"

TOOLCHAIN = "clang"
#TARGET_CXXFLAGS_append_toolchain-clang = " -stdlib=libc++ "

DEPENDS += "llvm-native libpcre lz4 libx11 libxpm libxft gsl fftw
libatomic-ops freetype glew xrootd"

inherit cmake pkgconfig pythonnative


do_configure_prepend(){
export FC=${GFORTRAN}
}

EXTRA_OECMAKE = "\
-Drootfit=ON \
-Dminuit2=ON \
-Dpython=ON \
-Dssl=ON \
-Dxrootd=ON \
-Dbuiltin_freetype=OFF \
-Dbuiltin_llvm=OFF \
-Dbuiltin_glew=OFF \
-Dastiff=OFF \
-Dasimage=OFF \
-Dbuiltin_afterimage=OFF \
-Dalien=OFF \
-Dvdt=OFF \
"

-- 
Giordon Stark
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Understanding "dev package contains non-symlink"

[Giordon Stark]

Hi,

So the good news is that this is at least the source code itself appears to
be written in a packaged-up-manner which makes some things easier to deal
with. It seems that all of the plugins are here:
https://github.com/xrootd/xrootd/blob/dad82068ae99859ebf40f65d95fe7c44f7db057e/src/XrdPlugins.cmake


where it seems to install to

install(
  TARGETS ${LIB_XRD_PSS} ${LIB_XRD_BWM} ${LIB_XRD_GPFS} ${LIB_XRD_ZCRC32}
${LIB_XRD_THROTTLE} ${LIB_XRD_N2NO2P}
  LIBRARY DESTINATION ${CMAKE_INSTALL_LIBDIR} )

While all other "non-plugins" also install to the same
"CMAKE_INSTALL_LIBDIR". I suppose it might be possible to patch this one
particular file to get the installs in a separate location? This seems like
potentially a short patch given that all plug-ins, from a cursory glance,
are installed with the same CMake instruction...

If not, I would be ok with adding

INSANE_SKIP_${PN} += "dev-so"

to my recipe along with the other two lines I've added (one to erase the
so-libs pattern for ${PN}-dev, and one to force all the *.so libs into
${PN}).

Would a third option be to just manually write out my ${PN} and ${PN}-dev
files to split up which are symlinks and which are not -- given that I'm
writing this recipe for a given version/configuration?

Giordon


On Fri, Jul 6, 2018 at 3:52 PM Andre McCurdy  wrote:

> On Fri, Jul 6, 2018 at 1:28 PM, Giordon Stark  wrote:
> > Hi,
> >
> > Been struggling to understand the differences here. This is what the
> > directory looks like
> >
> > kratsg@dc:/local/d4/gstark/poky/build$ ls
> >
> tmp/work/aarch64-poky-linux/xrootd/4.8.3-r0/packages-split/xrootd/usr/lib/
> > total 4.3M
> > drwxr-xr-x 2 kratsg atlas 4.0K Jun 28 16:13 .
> > drwxr-xr-x 5 kratsg atlas 4.0K Jun 28 16:13 ..
> > lrwxrwxrwx 1 kratsg atlas   19 Jun 28 16:13 libXrdAppUtils.so ->
> > libXrdAppUtils.so.1
> > lrwxrwxrwx 1 kratsg atlas   23 Jun 28 16:13 libXrdAppUtils.so.1 ->
> > libXrdAppUtils.so.1.0.0
> > -rwxr-xr-x 2 kratsg atlas  44K Jun 28 16:13 libXrdAppUtils.so.1.0.0
> > -rwxr-xr-x 2 kratsg atlas  15K Jun 28 16:13 libXrdBlacklistDecision-4.so
> > -rwxr-xr-x 2 kratsg atlas  59K Jun 28 16:13 libXrdBwm-4.so
> > -rwxr-xr-x 2 kratsg atlas  11K Jun 28 16:13 libXrdCksCalczcrc32-4.so
> > lrwxrwxrwx 1 kratsg atlas   13 Jun 28 16:13 libXrdCl.so -> libXrdCl.so.2
> > -rwxr-xr-x 2 kratsg atlas  27K Jun 28 16:13 libXrdClProxyPlugin-4.so
> > lrwxrwxrwx 1 kratsg atlas   17 Jun 28 16:13 libXrdClient.so ->
> > libXrdClient.so.2
> > lrwxrwxrwx 1 kratsg atlas   21 Jun 28 16:13 libXrdClient.so.2 ->
> > libXrdClient.so.2.0.0
> > -rwxr-xr-x 2 kratsg atlas 554K Jun 28 16:13 libXrdClient.so.2.0.0
> > lrwxrwxrwx 1 kratsg atlas   17 Jun 28 16:13 libXrdCl.so.2 ->
> > libXrdCl.so.2.0.0
> > -rwxr-xr-x 2 kratsg atlas 937K Jun 28 16:13 libXrdCl.so.2.0.0
> > lrwxrwxrwx 1 kratsg atlas   17 Jun 28 16:13 libXrdCrypto.so ->
> > libXrdCrypto.so.1
> > lrwxrwxrwx 1 kratsg atlas   21 Jun 28 16:13 libXrdCryptoLite.so ->
> > libXrdCryptoLite.so.1
> > lrwxrwxrwx 1 kratsg atlas   25 Jun 28 16:13 libXrdCryptoLite.so.1 ->
> > libXrdCryptoLite.so.1.0.0
> > -rwxr-xr-x 2 kratsg atlas 5.9K Jun 28 16:13 libXrdCryptoLite.so.1.0.0
> > lrwxrwxrwx 1 kratsg atlas   21 Jun 28 16:13 libXrdCrypto.so.1 ->
> > libXrdCrypto.so.1.0.0
> > -rwxr-xr-x 2 kratsg atlas  95K Jun 28 16:13 libXrdCrypto.so.1.0.0
> > lrwxrwxrwx 1 kratsg atlas   14 Jun 28 16:13 libXrdFfs.so ->
> libXrdFfs.so.2
> > lrwxrwxrwx 1 kratsg atlas   18 Jun 28 16:13 libXrdFfs.so.2 ->
> > libXrdFfs.so.2.0.0
> > -rwxr-xr-x 2 kratsg atlas  47K Jun 28 16:13 libXrdFfs.so.2.0.0
> > -rwxr-xr-x 2 kratsg atlas 156K Jun 28 16:13 libXrdFileCache-4.so
> > -rwxr-xr-x 2 kratsg atlas  15K Jun 28 16:13 libXrdN2No2p-4.so
> > -rwxr-xr-x 2 kratsg atlas  11K Jun 28 16:13 libXrdOssSIgpfsT-4.so
> > lrwxrwxrwx 1 kratsg atlas   16 Jun 28 16:13 libXrdPosix.so ->
> > libXrdPosix.so.2
> > lrwxrwxrwx 1 kratsg atlas   23 Jun 28 16:13 libXrdPosixPreload.so ->
> > libXrdPosixPreload.so.1
> > lrwxrwxrwx 1 kratsg atlas   27 Jun 28 16:13 libXrdPosixPreload.so.1 ->
> > libXrdPosixPreload.so.1.0.0
> > -rwxr-xr-x 2 kratsg atlas  67K Jun 28 16:13 libXrdPosixPreload.so.1.0.0
> > lrwxrwxrwx 1 kratsg atlas   20 Jun 28 16:13 libXrdPosix.so.2 ->
> > libXrdPosix.so.2.0.0
> > -rwxr-xr-x 2 kratsg atlas 128K Jun 28 16:13 libXrdPosix.so.2.0.0
> > -rwxr-xr-x 2 kratsg atlas  56K Jun 28 16:13 libXrdPss-4.so
> > -rwxr-xr-x 2 kratsg atlas  19K Jun 28 16:13 libXrdSecProt-4.so
> > -rwxr-xr-x 2 kratsg atlas 112K Jun 28 16:13 libXrdSecpwd-4.so
> > -rwxr-xr-x 2 kratsg atlas  35K Jun 28 16:13 libXrdSecsss-4.so
> &

Re: [yocto] Understanding "dev package contains non-symlink"

[Giordon Stark]

On Thu, Jun 28, 2018 at 7:37 PM Andre McCurdy  wrote:

> On Thu, Jun 28, 2018 at 3:53 PM, Burton, Ross 
> wrote:
> > Hi Giordan,
> >
> >
> https://wiki.yoctoproject.org/wiki/TipsAndTricks/Packaging_Prebuilt_Libraries
> > might be helpful to you.
> >
> > One useful thing would be to show us exactly what files are being
> > installed (and what files are symlinks).  It sounds like xrootd is
> > messing up library installation...
>
> Based on the logs, it looks like xrootd is installing both versioned
> shared libraries (e.g. "libXrdXml.so" is presumably a symlink to a
> real library named libXrdXml.so. ?) and it's ALSO
> installing a set of plug-ins (e.g. "libXrdThrottle-4.so").
>
> If so, then the real problem seems to be that the plug-ins are being
> installed in /usr/lib. To avoid tripping up the default packaging
> rules and QA tests, plug-ins should ideally be installed somewhere
> other than ${base_libdir} or ${libdir}.
>
> If you can fix the build so that the plug-ins (just the plug-ins, not
> the versioned shared libraries) get installed to a different directory
> then I guess you will be able remove the packaging rules over-rides
> and the QA errors will go away.
>
> If you can't fix the build to install the plug-ins in another
> directory, then you could keep the packaging rules over-rides that you
> have already and just ignore the "dev-so" QA test (unlike the
> "dev-elf" QA test, which you should never ignore, the consequences of
> ignoring the "dev-so" QA test are fairly benign - you will end up with
> .so symlinks in the run-time package, which doesn't do any real harm).
>
> > On 28 June 2018 at 22:19, Giordon Stark  wrote:
> >> Hi,
> >>
> >> I've read the emails in this mailing list. I'm mostly struggling to
> >> understand the situation for which "-dev package contains non-symlink
> .so"
> >> occurs. I understand that normally, one expects "*.so" files installed
> as
> >> part of the package, with symlinks to these versions in the "-dev"
> package.
> >> What I don't understand is the fix, and why this problem occurs in the
> first
> >> place.
> >>
> >> The recipe I'm working on in question is here: xrootd_4.8.3.bb (if
> this link
> >> doesn't work in the future, it's probably because I've merged this to
> >> master). This recipe is to install this piece of code:
> >> https://github.com/xrootd/xrootd.
> >>
> >> Here's an example of the errors:
> >>
> >> ERROR: xrootd-4.8.3-r0 do_package_qa: QA Issue: -dev package contains
> >> non-symlink .so: xrootd-dev path
> >>
> '/work/aarch64-poky-linux/xrootd/4.8.3-r0/packages-split/xrootd-dev/usr/lib/libXrdThrottle-4.so'
> >> -dev package contains non-symlink .so: xrootd-dev path
> >>
> '/work/aarch64-poky-linux/xrootd/4.8.3-r0/packages-split/xrootd-dev/usr/lib/libXrdSecsss-4.so'
> >> -dev package contains non-symlink .so: xrootd-dev path
> >>
> '/work/aarch64-poky-linux/xrootd/4.8.3-r0/packages-split/xrootd-dev/usr/lib/libXrdSecunix-4.so'
> >> -dev package contains non-symlink .so: xrootd-dev path
> >>
> '/work/aarch64-poky-linux/xrootd/4.8.3-r0/packages-split/xrootd-dev/usr/lib/libXrdSecpwd-4.so'
> >> -dev package contains non-symlink .so: xrootd-dev path
> >>
> '/work/aarch64-poky-linux/xrootd/4.8.3-r0/packages-split/xrootd-dev/usr/lib/libXrdN2No2p-4.so'
> >> -dev package contains non-symlink .so: xrootd-dev path
> >>
> '/work/aarch64-poky-linux/xrootd/4.8.3-r0/packages-split/xrootd-dev/usr/lib/libXrdSec-4.so'
> >> -dev package contains non-symlink .so: xrootd-dev path
> >>
> '/work/aarch64-poky-linux/xrootd/4.8.3-r0/packages-split/xrootd-dev/usr/lib/libXrdFileCache-4.so'
> >> -dev package contains non-symlink .so: xrootd-dev path
> >>
> '/work/aarch64-poky-linux/xrootd/4.8.3-r0/packages-split/xrootd-dev/usr/lib/libXrdSsiLog-4.so'
> >> -dev package contains non-symlink .so: xrootd-dev path
> >>
> '/work/aarch64-poky-linux/xrootd/4.8.3-r0/packages-split/xrootd-dev/usr/lib/libXrdCksCalczcrc32-4.so'
> >> -dev package contains non-symlink .so: xrootd-dev path
> >>
> '/work/aarch64-poky-linux/xrootd/4.8.3-r0/packages-split/xrootd-dev/usr/lib/libXrdBwm-4.so'
> >> -dev package contains non-symlink .so: xrootd-dev path
> >>
> '/work/aarch64-poky-linux/xrootd/4.8.3-r0/packages-split/xrootd-dev/usr/lib/libXrdBlacklistDecision-4.so'
> >> -dev package contains non-symlink .so: xrootd-dev path
> >>
> '/work/aarch64-poky-linux/xrootd/4.8.3

[yocto] Understanding "dev package contains non-symlink"

[Giordon Stark]

kages-split/xrootd/usr/lib/libXrdPosix.so'
non -dev/-dbg/nativesdk- package contains symlink .so: xrootd path
'/work/aarch64-poky-linux/xrootd/4.8.3-r0/packages-split/xrootd/usr/lib/libXrdUtils.so'
non -dev/-dbg/nativesdk- package contains symlink .so: xrootd path
'/work/aarch64-poky-linux/xrootd/4.8.3-r0/packages-split/xrootd/usr/lib/libXrdSsiShMap.so'
non -dev/-dbg/nativesdk- package contains symlink .so: xrootd path
'/work/aarch64-poky-linux/xrootd/4.8.3-r0/packages-split/xrootd/usr/lib/libXrdCl.so'
non -dev/-dbg/nativesdk- package contains symlink .so: xrootd path
'/work/aarch64-poky-linux/xrootd/4.8.3-r0/packages-split/xrootd/usr/lib/libXrdClient.so'
non -dev/-dbg/nativesdk- package contains symlink .so: xrootd path
'/work/aarch64-poky-linux/xrootd/4.8.3-r0/packages-split/xrootd/usr/lib/libXrdServer.so'
non -dev/-dbg/nativesdk- package contains symlink .so: xrootd path
'/work/aarch64-poky-linux/xrootd/4.8.3-r0/packages-split/xrootd/usr/lib/libXrdPosixPreload.so'
non -dev/-dbg/nativesdk- package contains symlink .so: xrootd path
'/work/aarch64-poky-linux/xrootd/4.8.3-r0/packages-split/xrootd/usr/lib/libXrdFfs.so'
[dev-so]
ERROR: xrootd-4.8.3-r0 do_package_qa: QA run found fatal errors. Please
consider fixing them.
ERROR: xrootd-4.8.3-r0 do_package_qa: Function failed: do_package_qa
ERROR: Logfile of failure stored in:
/local/d4/gstark/poky/build/tmp/work/aarch64-poky-linux/xrootd/4.8.3-r0/temp/log.do_package_qa.30048
ERROR: Task 
(/local/d4/gstark/meta-l1calo/recipes-core/root/xrootd_4.8.3.bb:do_package_qa)
failed with exit code '1'

I'm getting a bit confused as these errors didn't show up the first time.
And I suppose part of the confusing is about packaging vs installation.

Thanks,

Giordon
-- 
Giordon Stark
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Best practice for updating a single recipe in meta-openembedded?

[Giordon Stark]

Hi all,

I noticed on a 64b board, devmem2 isn't able to write 32b. I noticed,
surprisingly, that there's now a patch for this fix in master (
https://github.com/openembedded/meta-openembedded/commit/1bcd15ed5b31bdec492af99f671718d7a6eb887b
).

I'm currently on rocko, which doesn't have this additional change. Can I
just cherry-pick this commit onto meta-openembedded, or should I apply
these changes into my custom layer, and leave the meta-openembedded layer
untouched?

Thanks,

Giordon
-- 
Giordon Stark
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Setting a custom hostname using git revisions?

[Giordon Stark]

Hi all,

I looked at the bitbake manual, but if I have a custom layer that's checked
out at a specific revision, how can I access the variable containing the
revision to embed it into the hostname variable?

I would want to append the hostname variable in:
recipes-core/base-files/base-files_%.bbappend which is currently set to
"${MACHINE}".

Instead, I would like something along the lines of
"${MACHINE}-${LAYER_REV}".

Thanks,

Giordon
-- 
Giordon Stark
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Kernel configuration patches not persisting?

[Giordon Stark]

Hi Stephano,

I see. A large part of this confusion probably comes from the fact that
they're both using kconfig indeed. ARCH_ZYNQMP is actually used by the
u-boot-xlnx as well (maybe that makes things even more confusing).

Do both u-boot and linux-yocto accept kernel fragments? Is a kernel config
fragment detected by bitbake as a file ending in *.cfg and a full config as
a file called "defconfig"? This distinction isn't super clear in the manual.

In the meantime, I will add a bbappend and a kernel config fragment to
recipes-kernel/linux/ and report back.

G

On Wed, Apr 4, 2018 at 10:32 AM Stephano Cetola <
stephano.cet...@linux.intel.com> wrote:

> On 4/4/18 7:48 AM, Giordon Stark wrote:
> > Hi all,
> >
> > I have a custom board with custom kernel config changes. Because of
> > that, I append the u-boot recipe as well:
> >
> >
> https://github.com/kratsg/meta-l1calo/blob/master/recipes-bsp/u-boot/u-boot-xlnx_%25.bbappend
>
> >
> > with my machine.h and defconfig files
> > here:
> https://github.com/kratsg/meta-l1calo/tree/master/recipes-bsp/u-boot/files/gfex-prototype4
>
> >
> > I find that when I make a change in the defconfig, such as
> > "CONFIG_CPU_IDLE=n", bitbake properly recompiles all the necessary
> > components... however, when I look at the running kernel configuration:
> >
> > root@gfex-prototype4:~# cat /proc/config.gz | gunzip > run.config
> > root@gfex-prototype4:~# vi run.config
> > root@gfex-prototype4:~# cat run.config | grep CONFIG_CPU_IDLE
> > CONFIG_CPU_IDLE=y
> > # CONFIG_CPU_IDLE_GOV_LADDER is not set
> > CONFIG_CPU_IDLE_GOV_MENU=y
> >
> > it seems my change still wasn't propagated? I looked at the instructions
> > here
> > (
> https://www.yoctoproject.org/docs/latest/kernel-dev/kernel-dev.html#changing-the-configuration
> )
> > but I'm not sure I want to duplicate my defconfig file into a second
> > location to bbappend the linux-yocto.
> >
> > Have I done something wrong? Am I missing something else?
> >
> > Giordon
> > --
> > Giordon Stark
>
> Hey Giordon,
>
> It looks like you're confusing two topics: u-boot and kernel configuration.
>
> Both u-boot and the kernel use kconfig. This can confuse folks that are
> new to bootloader/kernel work.
>
> Looking at your layer, you're actually interested in changing the
> kernel's configuration rather than u-boot. For example, on the
> gfex-prototype4 defconfig, you set ARCH_ZYNQMP, which is a kernel config
> for the Xilinx Zynq boards. You probably want to add a bbappend for your
> kernel and add the defconfig to that recipe.
>
> Cheers,
> Stephano
>
> --
Giordon Stark
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Kernel configuration patches not persisting?

[Giordon Stark]

Hi all,

I have a custom board with custom kernel config changes. Because of that, I
append the u-boot recipe as well:

https://github.com/kratsg/meta-l1calo/blob/master/recipes-bsp/u-boot/u-boot-xlnx_%25.bbappend


with my machine.h and defconfig files here:
https://github.com/kratsg/meta-l1calo/tree/master/recipes-bsp/u-boot/files/gfex-prototype4


I find that when I make a change in the defconfig, such as "
CONFIG_CPU_IDLE=n", bitbake properly recompiles all the necessary
components... however, when I look at the running kernel configuration:

root@gfex-prototype4:~# cat /proc/config.gz | gunzip > run.config
root@gfex-prototype4:~# vi run.config
root@gfex-prototype4:~# cat run.config | grep CONFIG_CPU_IDLE
CONFIG_CPU_IDLE=y
# CONFIG_CPU_IDLE_GOV_LADDER is not set
CONFIG_CPU_IDLE_GOV_MENU=y

it seems my change still wasn't propagated? I looked at the instructions
here (
https://www.yoctoproject.org/docs/latest/kernel-dev/kernel-dev.html#changing-the-configuration)
but I'm not sure I want to duplicate my defconfig file into a second
location to bbappend the linux-yocto.

Have I done something wrong? Am I missing something else?

Giordon
-- 
Giordon Stark
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] python-fcntl missing in rocko?

[Giordon Stark]

Indeed,

I seem to have gotten lucky by having it included without an explicit
RDEPENDS/DEPENDS line for it. I've added it manually and now it's included
:) Thanks.

Giordon

On Tue, Mar 27, 2018 at 1:32 PM Burton, Ross <ross.bur...@intel.com> wrote:

> python-core is just "an arbitrary subset of the python libraries",
> you'd do better by including python-modules in your image which is all
> of Python.
>
> Or use oe-pkgdata-util to search what package contains the fcntl module.
>
> Ross
>
> On 27 March 2018 at 17:50, Giordon Stark <kra...@gmail.com> wrote:
> > Hi all,
> >
> > When I switched from pyro to rocko, using `python-core` -- I'm noticing
> that
> > the fcntl module in python2 is missing. Is there a recipe to add to get
> it
> > back?
> >
> > Thanks,
> >
> > Giordon
> > --
> > Giordon Stark
> >
> > --
> > ___________
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
> >
>
-- 
Giordon Stark
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] python-fcntl missing in rocko?

[Giordon Stark]

Hi all,

When I switched from pyro to rocko, using `python-core` -- I'm noticing
that the fcntl module in python2 is missing. Is there a recipe to add to
get it back?

Thanks,

Giordon
-- 
Giordon Stark
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] No module named setuptools -- even with "inherit setuptools"?

[Giordon Stark]

Hi Ross,

I am confused, as it seems to have been running /usr/bin/python at some
point along the line... which is strange. I decided to take these two lines

DEPENDS = "python python-six"
RDEPENDS_${PN} += "python-lang python-shell python-six python-debugger"

and rewrite them into

RDEPENDS_${PN} += "python-core python-six python-debugger"

and now things work. That's the only change. I think this might be DEPENDS
vs RDEPENDS that screwed me up (and the naming of python recipes).. but I'm
not really sure.. The working recipe is below:

DESCRIPTION = "Python declarative parser for binary data"
HOMEPAGE = "http://construct.readthedocs.org/en/latest/;
SECTION = "devel/python"
LICENSE = "BSD-3-Clause"
LIC_FILES_CHKSUM = "file://LICENSE;md5=3fd0f2c25089e629957285e6bc402a20"

PYPI_PACKAGE = "construct"
inherit pypi setuptools

SRC_URI[md5sum] = "39407f91407138f687ea2ecf8d758a1f"
SRC_URI[sha256sum] =
"c23ef47fd5751d821e5c17d9b3b02d1f3c465e66b8a205b9c791c4abef747138"

RDEPENDS_${PN} += "python-core python-six python-debugger"


On Fri, Mar 23, 2018 at 2:53 PM Burton, Ross <ross.bur...@intel.com> wrote:

> Should work, as the setuptools class depends on
> python-distribute-native which is provided by
> python-setuptools-native, and the class also inherits pythonnative so
> it should be running the python from the sysroot and not the host
> python.
>
> I'd verify that it's not explicitly running /usr/bin/python at some
> point, instead of the python binary in $PATH.
>
> Ross
>
> On 23 March 2018 at 18:46, Giordon Stark <kra...@gmail.com> wrote:
> > Hi,
> >
> > I'm a bit perplexed. I don't know what I'm doing wrong here, but this is
> the
> > log data:
> >
> > Log data follows:
> > | DEBUG: Executing shell function do_compile
> > | Traceback (most recent call last):
> > |   File "setup.py", line 2, in 
> > | from setuptools import setup
> > | ImportError: No module named setuptools
> > | ERROR: python setup.py build execution failed.
> > | WARNING:
> >
> /local/d4/gstark/poky/build/tmp/work/aarch64-poky-linux/python-construct/2.9.39-r0/temp/run.do_compile.3286:1
> > exit 1 from 'exit 1'
> > | ERROR: Function failed: do_compile (log file is located at
> >
> /local/d4/gstark/poky/build/tmp/work/aarch64-poky-linux/python-construct/2.9.39-r0/temp/log.do_compile.3286)
> > ERROR: Task
> > (/local/d4/gstark/meta-l1calo/recipes-python/python-construct_2.9.39.bb:
> do_compile)
> > failed with exit code '1'
> >
> > with the recipe looking like this... (below). Any ideas?
> >
> > DESCRIPTION = "Python declarative parser for binary data"
> > HOMEPAGE = "http://construct.readthedocs.org/en/latest/;
> > SECTION = "devel/python"
> > LICENSE = "BSD-3-Clause"
> > LIC_FILES_CHKSUM = "file://LICENSE;md5=3fd0f2c25089e629957285e6bc402a20"
> >
> > PYPI_PACKAGE = "construct"
> > inherit pypi setuptools
> >
> > SRC_URI[md5sum] = "39407f91407138f687ea2ecf8d758a1f"
> > SRC_URI[sha256sum] =
> > "c23ef47fd5751d821e5c17d9b3b02d1f3c465e66b8a205b9c791c4abef747138"
> >
> > DEPENDS = "python python-six"
> > RDEPENDS_${PN} += "python-lang python-shell python-six python-debugger"
> > --
> > Giordon Stark
> >
> > --
> > ___
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
> >
>
-- 
Giordon Stark
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] No module named setuptools -- even with "inherit setuptools"?

[Giordon Stark]

Hi,

I'm a bit perplexed. I don't know what I'm doing wrong here, but this is
the log data:

Log data follows:
| DEBUG: Executing shell function do_compile
| Traceback (most recent call last):
|   File "setup.py", line 2, in 
| from setuptools import setup
| ImportError: No module named setuptools
| ERROR: python setup.py build execution failed.
| WARNING:
/local/d4/gstark/poky/build/tmp/work/aarch64-poky-linux/python-construct/2.9.39-r0/temp/run.do_compile.3286:1
exit 1 from 'exit 1'
| ERROR: Function failed: do_compile (log file is located at
/local/d4/gstark/poky/build/tmp/work/aarch64-poky-linux/python-construct/2.9.39-r0/temp/log.do_compile.3286)
ERROR: Task
(/local/d4/gstark/meta-l1calo/recipes-python/python-construct_2.9.39.bb:do_compile)
failed with exit code '1'

with the recipe looking like this... (below). Any ideas?

DESCRIPTION = "Python declarative parser for binary data"
HOMEPAGE = "http://construct.readthedocs.org/en/latest/;
SECTION = "devel/python"
LICENSE = "BSD-3-Clause"
LIC_FILES_CHKSUM = "file://LICENSE;md5=3fd0f2c25089e629957285e6bc402a20"

PYPI_PACKAGE = "construct"
inherit pypi setuptools

SRC_URI[md5sum] = "39407f91407138f687ea2ecf8d758a1f"
SRC_URI[sha256sum] =
"c23ef47fd5751d821e5c17d9b3b02d1f3c465e66b8a205b9c791c4abef747138"

DEPENDS = "python python-six"
RDEPENDS_${PN} += "python-lang python-shell python-six python-debugger"
-- 
Giordon Stark
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Could not invoke DNF with python package (Unable to find a match)

[Giordon Stark]

Well,

This is a bit confusing -- but apparently my *.bb files needed an "inherit
setuptools" at the top to make this happen. I thought this was already
being done in the pypi.bbclass ... but apparently that's not done anymore.
Is this an expected change?

Giordon

On Sat, Mar 17, 2018 at 12:16 PM Giordon Stark <kra...@gmail.com> wrote:

> Hi,
>
> I'm a bit confused by this error, since as far as I can tell, bitbake sees
> this particular recipe I wrote...
>
> inc file:
> https://github.com/kratsg/meta-l1calo/blob/master/recipes-python/python-ironman.inc
>
> specific version:
> https://github.com/kratsg/meta-l1calo/blob/master/recipes-python/python-ironman_0.2.13.bb
>
>
> ERROR: zynq-base-1.0-r0 do_rootfs: Could not invoke dnf. Command
> '/local/d4/gstark/poky/build/tmp/work/gfex_prototype3a-poky-linux/zynq-base/1.0-r0/recipe-sysroot-native/usr/bin/dnf
> -y -c
> /local/d4/gstark/poky/build/tmp/work/gfex_prototype3a-poky-linux/zynq-base/1.0-r0/rootfs/etc/dnf/dnf.conf
> --setopt=reposdir=/local/d4/gstark/poky/build/tmp/work/gfex_prototype3a-poky-linux/zynq-base/1.0-r0/rootfs/etc/yum.repos.d
> --repofrompath=oe-repo,/local/d4/gstark/poky/build/tmp/work/gfex_prototype3a-poky-linux/zynq-base/1.0-r0/oe-rootfs-repo
> --installroot=/local/d4/gstark/poky/build/tmp/work/gfex_prototype3a-poky-linux/zynq-base/1.0-r0/rootfs
> --setopt=logdir=/local/d4/gstark/poky/build/tmp/work/gfex_prototype3a-poky-linux/zynq-base/1.0-r0/temp
> --nogpgcheck install locale-base-en-us locale-base-en-gb
> packagegroup-core-boot run-postinsts packagegroup-core-ssh-openssh devmem2
> init-clock python-ironman packagegroup-base-extended' returned 1:
> Added oe-repo repo from
> file:///local/d4/gstark/poky/build/tmp/work/gfex_prototype3a-poky-linux/zynq-base/1.0-r0/oe-rootfs-repo
> Last metadata expiration check: 0:00:00 ago on Sat Mar 17 17:11:44 2018
> UTC.
> No package python-ironman available.
> Error: Unable to find a match
>
> ERROR: zynq-base-1.0-r0 do_rootfs: Function failed: do_rootfs
> ERROR: Logfile of failure stored in:
> /local/d4/gstark/poky/build/tmp/work/gfex_prototype3a-poky-linux/zynq-base/1.0-r0/temp/log.do_rootfs.24270
> ERROR: Task 
> (/local/d4/gstark/meta-l1calo/recipes-core/images/zynq-base.bb:do_rootfs)
> failed with exit code '1'
>
> so I double-checked that the recipe was discoverable:
>
> kratsg@dc:/local/d4/gstark/poky/build$ bitbake-layers show-recipes
> python-ironman
> === Matching recipes: ===
> python-ironman:
>   meta-l1calo  0.2.13
>
> Any ideas if I wrote this python recipe incorrectly? If I inherit from
> pypi, it should install this for me as an rpm that can be picked up by
> bitbake, right?
>
> Giordon
> --
> Giordon Stark
>
-- 
Giordon Stark
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Could not invoke DNF with python package (Unable to find a match)

[Giordon Stark]

Hi,

I'm a bit confused by this error, since as far as I can tell, bitbake sees
this particular recipe I wrote...

inc file:
https://github.com/kratsg/meta-l1calo/blob/master/recipes-python/python-ironman.inc

specific version:
https://github.com/kratsg/meta-l1calo/blob/master/recipes-python/python-ironman_0.2.13.bb


ERROR: zynq-base-1.0-r0 do_rootfs: Could not invoke dnf. Command
'/local/d4/gstark/poky/build/tmp/work/gfex_prototype3a-poky-linux/zynq-base/1.0-r0/recipe-sysroot-native/usr/bin/dnf
-y -c
/local/d4/gstark/poky/build/tmp/work/gfex_prototype3a-poky-linux/zynq-base/1.0-r0/rootfs/etc/dnf/dnf.conf
--setopt=reposdir=/local/d4/gstark/poky/build/tmp/work/gfex_prototype3a-poky-linux/zynq-base/1.0-r0/rootfs/etc/yum.repos.d
--repofrompath=oe-repo,/local/d4/gstark/poky/build/tmp/work/gfex_prototype3a-poky-linux/zynq-base/1.0-r0/oe-rootfs-repo
--installroot=/local/d4/gstark/poky/build/tmp/work/gfex_prototype3a-poky-linux/zynq-base/1.0-r0/rootfs
--setopt=logdir=/local/d4/gstark/poky/build/tmp/work/gfex_prototype3a-poky-linux/zynq-base/1.0-r0/temp
--nogpgcheck install locale-base-en-us locale-base-en-gb
packagegroup-core-boot run-postinsts packagegroup-core-ssh-openssh devmem2
init-clock python-ironman packagegroup-base-extended' returned 1:
Added oe-repo repo from
file:///local/d4/gstark/poky/build/tmp/work/gfex_prototype3a-poky-linux/zynq-base/1.0-r0/oe-rootfs-repo
Last metadata expiration check: 0:00:00 ago on Sat Mar 17 17:11:44 2018 UTC.
No package python-ironman available.
Error: Unable to find a match

ERROR: zynq-base-1.0-r0 do_rootfs: Function failed: do_rootfs
ERROR: Logfile of failure stored in:
/local/d4/gstark/poky/build/tmp/work/gfex_prototype3a-poky-linux/zynq-base/1.0-r0/temp/log.do_rootfs.24270
ERROR: Task 
(/local/d4/gstark/meta-l1calo/recipes-core/images/zynq-base.bb:do_rootfs)
failed with exit code '1'

so I double-checked that the recipe was discoverable:

kratsg@dc:/local/d4/gstark/poky/build$ bitbake-layers show-recipes
python-ironman
=== Matching recipes: ===
python-ironman:
  meta-l1calo  0.2.13

Any ideas if I wrote this python recipe incorrectly? If I inherit from
pypi, it should install this for me as an rpm that can be picked up by
bitbake, right?

Giordon
-- 
Giordon Stark
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] scipy recipe

[Giordon Stark]

Seems like the SRC_URI isn't correct. I don't see an obvious place to get
tarballs for scipy except from github (and I know that tends to not be
reliable but...)

https://github.com/scipy/scipy/archive/v1.0.0.tar.gz

Giordon

On Fri, Mar 16, 2018 at 11:51 AM Peter Balazovic <balazovic.pe...@gmail.com>
wrote:

> per using recipe https://github.com/scipy/scipy/issues/8226
>
>
> SUMMARY = "Scientific Library for Python"
> SECTION = "devel/python"
> HOMEPAGE = "https://pypi.python.org/pypi/scipy;
>
> LICENSE = "BSD-3-Clause"
> LIC_FILES_CHKSUM = "file://LICENSE.txt;md5=d0db8f4148a3d5534cfb93be78f9287c"
>
> PYPI_PACKAGE="scipy"
>
> SRC_URI[md5sum] = "53fa34bd3733a9a4216842b6000f7316"
> SRC_URI[sha256sum] = 
> "87ea1f11a0e9ec08c264dc64551d501fa307289460705f6fccd84cbfc7926d10"
>
> inherit pypi setuptools distutils
>
> RDEPENDS_${PN} += "python-core python-numpy-native python-distutils"
> DEPENDS += "python-numpy"
>
>
> I am getting error to fetch scipy do_fetch error
>
>
> WARNING: scipy-1.0-r0 do_fetch: Failed to fetch URL
> https://files.pythonhosted.org/packages/source/s/scipy/scipy-1.0.tar.gz,
> attempting MIRRORS if available
> ERROR: scipy-1.0-r0 do_fetch: Fetcher failure: Fetch command export
> DBUS_SESSION_BUS_ADDRESS="unix:abstract=/tmp/dbus-idNNJsmT3C"; export
> SSH_AUTH_SOCK="/run/user/1000/keyring/ssh"; export ftp_proxy=
> --progress=dot -v failed with exit code 8, output:
> --2018-03-16 17:43:34--
> https://files.pythonhosted.org/packages/source/s/scipy/scipy-1.0.tar.gz
> Resolving files.pythonhosted.org (files.pythonhosted.org)...
> 151.101.17.63, 2a04:4e42:4::319
> Connecting to files.pythonhosted.org 
> (files.pythonhosted.org)|151.101.17.63|:443...
> connected.
> HTTP request sent, awaiting response... 404 Not Found
> 2018-03-16 17:43:35 ERROR 404: Not Found.
>
> Any help?
>
>
> On Thu, Mar 15, 2018 at 9:35 PM, Randy MacLeod <
> randy.macl...@windriver.com> wrote:
>
>> On 2018-03-15 01:56 PM, Peter Balazovic wrote:
>>
>>> Hello all,
>>>
>>> I wonder if there is scipy recipe available?
>>>
>>
>> Not yet:
>>
>> https://layers.openembedded.org/layerindex/branch/master/recipes/?q=scipy
>>
>> It appears to be blocked by:
>>https://github.com/scipy/scipy/issues/8226
>> but apparently that's a bitbake issue, not a spip one.
>> Care to take a look?
>>
>>
>>> Thanks.
>>>
>>>
>>>
>>
>> --
>> # Randy MacLeod.  WR Linux
>> # Wind River an Intel Company
>>
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
Giordon Stark
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] scipy recipe

[Giordon Stark]

gt; | config.add_subpackage('linalg')
> > |   File "/usr/lib/python2.7/site-packages/numpy/distutils/misc_util.py",
> > line 1003, in add_subpackage
> > | caller_level = 2)
> > |   File "/usr/lib/python2.7/site-packages/numpy/distutils/misc_util.py",
> > line 972, in get_subpackage
> > | caller_level = caller_level + 1)
> > |   File "/usr/lib/python2.7/site-packages/numpy/distutils/misc_util.py",
> > line 909, in _get_configuration_from_setup_py
> > | config = setup_module.configuration(*args)
> > |   File "scipy/linalg/setup.py", line 19, in configuration
> > | raise NotFoundError('no lapack/blas resources found')
> > | numpy.distutils.system_info.NotFoundError: no lapack/blas resources
> found
> > | ERROR: Function failed: do_compile (log file is located at
> > /scipy/1.0.0-r0/temp/log.do_compile.8708)
> > ERROR: Task
> >
> (/sources/meta-openembedded/meta-python/recipes-devtools/python/scipy_1.0.0.bb:
> do_compile)
> > failed with exit code '1'
> > NOTE: Tasks Summary: Attempted 8394 tasks of which 8382 didn't need to be
> > rerun and 1 failed.
> >
> >
> > On Fri, Mar 16, 2018 at 6:36 PM, Burton, Ross <ross.bur...@intel.com>
> wrote:
> >
> >> To change the version, change the filename of the recipe.
> >>
> >> Also, please remember the CC the list.
> >>
> >> Ross
> >>
> >> On 16 March 2018 at 17:30, Peter Balazovic <balazovic.pe...@gmail.com>
> >> wrote:
> >>
> >>> I did download from
> https://github.com/scipy/scipy/archive/v1.0.0.tar.gz
> >>> and cc to /downloads and same still issue ...
> >>> as mentioned  should be version is 1.0.0
> >>> where to change it to point to correct version & file?
> >>>
> >>> On Fri, Mar 16, 2018 at 5:57 PM, Burton, Ross <ross.bur...@intel.com>
> >>> wrote:
> >>>
> >>>> You're getting a "file not found" for the URL it is looking for.
> >>>> According to https://pypi.python.org/pypi/scipy, the version is 1.0.0
> >>>> not 1.0.
> >>>>
> >>>> Ross
> >>>>
> >>>> On 16 March 2018 at 16:50, Peter Balazovic <balazovic.pe...@gmail.com
> >
> >>>> wrote:
> >>>>
> >>>>> per using recipe https://github.com/scipy/scipy/issues/8226
> >>>>>
> >>>>>
> >>>>> SUMMARY = "Scientific Library for Python"
> >>>>> SECTION = "devel/python"
> >>>>> HOMEPAGE = "https://pypi.python.org/pypi/scipy;
> >>>>>
> >>>>> LICENSE = "BSD-3-Clause"
> >>>>> LIC_FILES_CHKSUM =
> "file://LICENSE.txt;md5=d0db8f4148a3d5534cfb93be78f9287c"
> >>>>>
> >>>>> PYPI_PACKAGE="scipy"
> >>>>>
> >>>>> SRC_URI[md5sum] = "53fa34bd3733a9a4216842b6000f7316"
> >>>>> SRC_URI[sha256sum] =
> "87ea1f11a0e9ec08c264dc64551d501fa307289460705f6fccd84cbfc7926d10"
> >>>>>
> >>>>> inherit pypi setuptools distutils
> >>>>>
> >>>>> RDEPENDS_${PN} += "python-core python-numpy-native python-distutils"
> >>>>> DEPENDS += "python-numpy"
> >>>>>
> >>>>>
> >>>>> I am getting error to fetch scipy do_fetch error
> >>>>>
> >>>>>
> >>>>> WARNING: scipy-1.0-r0 do_fetch: Failed to fetch URL
> >>>>>
> https://files.pythonhosted.org/packages/source/s/scipy/scipy-1.0.tar.gz,
> >>>>> attempting MIRRORS if available
> >>>>> ERROR: scipy-1.0-r0 do_fetch: Fetcher failure: Fetch command export
> >>>>> DBUS_SESSION_BUS_ADDRESS="unix:abstract=/tmp/dbus-idNNJsmT3C"; export
> >>>>> SSH_AUTH_SOCK="/run/user/1000/keyring/ssh"; export ftp_proxy=
> >>>>> --progress=dot -v failed with exit code 8, output:
> >>>>> --2018-03-16 17:43:34--  https://files.pythonhosted.org
> >>>>> /packages/source/s/scipy/scipy-1.0.tar.gz
> >>>>> Resolving files.pythonhosted.org (files.pythonhosted.org)...
> >>>>> 151.101.17.63, 2a04:4e42:4::319
> >>>>> Connecting to files.pythonhosted.org (files.pythonhosted.org
> )|151.101.17.63|:443...
> >>>>> connected.
> >>>>> HTTP request sent, awaiting response... 404 Not Found
> >>>>> 2018-03-16 17:43:35 ERROR 404: Not Found.
> >>>>>
> >>>>> Any help?
> >>>>>
> >>>>>
> >>>>> On Thu, Mar 15, 2018 at 9:35 PM, Randy MacLeod <
> >>>>> randy.macl...@windriver.com> wrote:
> >>>>>
> >>>>>> On 2018-03-15 01:56 PM, Peter Balazovic wrote:
> >>>>>>
> >>>>>>> Hello all,
> >>>>>>>
> >>>>>>> I wonder if there is scipy recipe available?
> >>>>>>>
> >>>>>>
> >>>>>> Not yet:
> >>>>>>
> >>>>>> https://layers.openembedded.org/layerindex/branch/master/rec
> >>>>>> ipes/?q=scipy
> >>>>>>
> >>>>>> It appears to be blocked by:
> >>>>>>https://github.com/scipy/scipy/issues/8226
> >>>>>> but apparently that's a bitbake issue, not a spip one.
> >>>>>> Care to take a look?
> >>>>>>
> >>>>>>
> >>>>>>> Thanks.
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> # Randy MacLeod.  WR Linux
> >>>>>> # Wind River an Intel Company
> >>>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>> ___
> >>>>> yocto mailing list
> >>>>> yocto@yoctoproject.org
> >>>>> https://lists.yoctoproject.org/listinfo/yocto
> >>>>>
> >>>>>
> >>>>
> >>>
> >>
> >
> >
> >
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
Giordon Stark
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Can SRC_URI look in the same place for two different machines?

[Giordon Stark]

Right, so the problem for me is that there seems to be two ways to do this:

MACHINEOVERRIDES .= ":machine3" (for 3a, 3b)

or

FILESEXTRAPATHS_append_machine3a = "${THISDIR}/files/machine3/"
FILESEXTRAPATHS_append_machine3b = "${THISDIR}/files/machine3/"

But it's not clear to me which is better or fits with the philosophy of
yocto/bitbake.

Giordon

On Fri, Mar 16, 2018 at 11:48 AM Robert P. J. Day <rpj...@crashcourse.ca>
wrote:

> On Fri, 16 Mar 2018, Burton, Ross wrote:
>
> > On 15 March 2018 at 14:07, Giordon Stark <kra...@gmail.com> wrote:
> >   So for my device trees, I'm finding some files are duplicated. In
> particular some of my
> >   dtsi files are going to be the same amongst a few boards we're
> using, so I would like
> >   to have each machine name distinct so that
> >
> > FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
> >
> > files/${MACHINE}/${MACHINE}.dts
> >
> > is picked up, while still having
> >
> > files/common/*.dtsi picked up as well. As an example of my SRC_URI
> appends:
> >
> > SRC_URI_append_gfex-prototype1b = " \
> > file://skeleton.dtsi  \
> > file://pl.dtsi\
> > file://zynq-7000.dtsi \
> > file://system.dts \
> > "
> >
> > SRC_URI_append_gfex-prototype2  = " \
> > file://skeleton.dtsi   \
> > file://pl.dtsi \
> > file://zynq-7000.dtsi  \
> > file://system.dts  \
> > "
> >
> > I suspect I do something with OVERRIDES in the
> > conf/machine/${MACHINE}.conf file but not sure...
> >
> >
> > Can't you just put common files in files/file.dtsi and then the
> > machine-specific ones in files/[machine]/?
>
>   isn't this precisely what MACHINEOVERRIDES is for?
>
> rday

-- 
Giordon Stark
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Can SRC_URI look in the same place for two different machines?

[Giordon Stark]

Hi,

I would do that, but what I want to do is something like this:

Machine1
Machine2
Machine3a
Machine3b
Machine4

I want 3a/3b to have some shared dtsi files, but these should not be shared
with machines 1, 2, 4. I'm not sure it's just a matter of placing it under
files/ because I don't want those picked up by the non-3 machines.

G

On Fri, Mar 16, 2018 at 11:42 AM Burton, Ross <ross.bur...@intel.com> wrote:

> On 15 March 2018 at 14:07, Giordon Stark <kra...@gmail.com> wrote:
>
>> So for my device trees, I'm finding some files are duplicated. In
>> particular some of my dtsi files are going to be the same amongst a few
>> boards we're using, so I would like to have each machine name distinct so
>> that
>>
>> FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
>>
>> files/${MACHINE}/${MACHINE}.dts
>>
>> is picked up, while still having
>>
>> files/common/*.dtsi picked up as well. As an example of my SRC_URI
>> appends:
>>
>> SRC_URI_append_gfex-prototype1b = " \
>> file://skeleton.dtsi  \
>> file://pl.dtsi\
>> file://zynq-7000.dtsi \
>> file://system.dts \
>> "
>>
>> SRC_URI_append_gfex-prototype2  = " \
>> file://skeleton.dtsi   \
>> file://pl.dtsi \
>> file://zynq-7000.dtsi  \
>> file://system.dts  \
>> "
>>
>> I suspect I do something with OVERRIDES in the
>> conf/machine/${MACHINE}.conf file but not sure...
>>
>
> Can't you just put common files in files/file.dtsi and then the
> machine-specific ones in files/[machine]/?
>
> Ross
>
-- 
Giordon Stark
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Can SRC_URI look in the same place for two different machines?

[Giordon Stark]

Hi,

So for my device trees, I'm finding some files are duplicated. In
particular some of my dtsi files are going to be the same amongst a few
boards we're using, so I would like to have each machine name distinct so
that

FILESEXTRAPATHS_prepend := "${THISDIR}/files:"

files/${MACHINE}/${MACHINE}.dts

is picked up, while still having

files/common/*.dtsi picked up as well. As an example of my SRC_URI appends:

SRC_URI_append_gfex-prototype1b = " \
file://skeleton.dtsi  \
file://pl.dtsi\
file://zynq-7000.dtsi \
file://system.dts \
"

SRC_URI_append_gfex-prototype2  = " \
file://skeleton.dtsi   \
file://pl.dtsi \
file://zynq-7000.dtsi  \
file://system.dts  \
"

I suspect I do something with OVERRIDES in the conf/machine/${MACHINE}.conf
file but not sure...

Thanks,

Giordon
-- 
Giordon Stark
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [yocto-announce] [ANNOUNCEMENT] Yocto Project 2.4.2 (rocko-18.0.2) Released

[Giordon Stark]

time/buildcpio: Use our own mirror for source
>> binutils: Convert SRC_URI and SRCREV to weak defines
>> binutils: update to 2.29.1
>> acpica: fix build with x32
>> boost: fix build with x32 and musl
>> runqemu: Add workaround for APIC hang on pre 4.15 kernels on qemux86
>> glib-2.0: Add python3 modules required by gdbus-codegen
>> lib/oe/patch: add missing import
>> bmap-tools: fix RDEPENDS and update SRC_URI
>> rm_work: remove debugging statements
>> kernel-fitimage: Fix bad image type replacement for aarch64
>> image-live.bbclass: add MLPREFIX to core-image-minimal-initramfs
>> image-live.bbclass: print warn when initramfs is invalid
>> wic: Fix a path to a psuedo state directory (PSEUDO_LOCALSTATEDIR).
>> waf.bbclass: explicitly pass bindir and libdir if supported
>> kernel.bbclass: Fix do_sizecheck behaviour
>> image_types: btrfs use sparse file creation
>> rm_work: Handle race with -inital tasks
>> linux-yocto/4.12: CQM and kmemleak fixes
>> linux-yocto/4.12: common-pc*: enable X2APIC by default
>> linux-yocto/4.12: update to v.4.12.18
>> linux-yocto/4.12: bug fixes and feature backports
>> linux-yocto/4.x: configuration updates
>> linux-yocto/4.12: ipv4 stable backport and config changes
>> linux-yocto/4.12: bug fixes and VRF feature addition
>> linux-yocto/4.12: update to v4.12.16
>> systemd: fix segfault when terminating systemd --test
>> recipetool: create: fix conflict between SRCREV and tag
>> libxslt: use HTTP instead of FTP in SRC_URI
>> ovmf: Fix build failure for PARALLEL_MAKE with no space
>> kernel-yocto: ensure that only a single defconfig is processed
>> kernel-yocto: Stop the build if defconfig is missing
>> kernel-yocto: ensure sccs variable is set when using KBUILD_DEFCONFIG
>> linux-yocto/4.9: update to v4.9.65
>> linux-yocto/4.12: iwlwifi calltrace fixes and configuration warning
>> cleanups
>> linux-yocto/4.9: update to v4.9.61
>> rootfs-postcommands.bbclass: ensure that rootfs gets mounted ro
>> connman.inc: do not check IMAGE_FEATURES
>> templates/layer.conf: remove backslash to enable bbappend setting
>> systemd: allow dots in arguments to template units
>> package_manager: force dnf to refresh the cache
>> meta-selftest: fix upstream version checks for devtool test recipes
>> mtd-utils: fix flash_eraseall installation conflict
>> wpa-supplicant: add a missing WPA_COMMON_CTRL_IFACE definition
>> update-alternatives.bbclass: refuse to manage SysV init scripts
>> Revert "classes: Fix alternatives and rc.d ordering"
>> initscripts: rrecommend initscripts-functions
>> lsbinitscripts: don't use update-alternatives
>> initscripts: don't use update-alternatives
>> sysklogd: don't use update-alternatives
>> install*.sh: add short sleep after parted commands
>> init-install: fix grub-install command
>> initramfs-module-install: Remove allarch and FILESEXTRAPATHS
>> initramfs-framework: add install module
>> initramfs-module-install-efi: update summary
>> initramfs-module-install-efi: point to original copy and delete new file
>> wic: support filesystem label for rawcopy
>> openssl: fix runtime errors with Thumb2 when using binutils 2.29
>> openssl: Upgrade 1.1.0f -> 1.1.0g
>> openssl10: fix runtime errors with Thumb2 when using binutils 2.29
>> openssl10: Upgrade 1.0.2l -> 1.0.2m
>> python[3]-setuptools: inherit setuptools
>> local.conf.sample: Weakly set BB_DISKMON_DIRS
>> documentation: Prepped manual set for a 2.4.1 point release
>> bitbake: toaster: add 'nobuild' option to Toaster
>> bitbake: toaster: landing page show cmdline capture
>> bitbake: toaster: enable custom env support for shell calls
>> bitbake: toaster: some recipe events do not include packages
>> bitbake: toaster: update Toaster for Django 1.11
>> bitbake: toaster: unset BBPATH before starting bbserver for backwards
>> compatibility
>> populate_sdk_ext: Use prebuilt uninative tarball
>> makefile: Removed "yocto-environment.png" from tar list of mega-manual
>> ref-manual: Fixed redundant link for "build system"
>> ref-manual: Added new terms to Yocto Project Terms section.
>> dev-manual: Updated bitbake-layers overview section.
>> ref-manual: 2.4 Migration Revisions
>> build-appliance: Fix branch name
>> --
>> ___
>> yocto-announce mailing list
>> yocto-annou...@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto-announce
>>
>
>
>
> --
> Ricardo Ribalda
>
>
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
Giordon Stark
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Bitbake recipe using CMake that requires python-six as part of compiling?

[Giordon Stark]

Is there a good recipe to follow where the normal rules apply for packaging
and such? I had a hard time finding one that wasn't a rabbit-hole of *.inc
files.

Giordon

On Tue, Mar 6, 2018 at 4:23 PM Andre McCurdy <armccu...@gmail.com> wrote:

> On Tue, Mar 6, 2018 at 2:12 PM, Giordon Stark <kra...@gmail.com> wrote:
> > Hi Andre,
> >
> > I tried without
> >
> > FILES_${PN}_append = "${includedir}/open62541.h"
> >
> > and got a QA error about a file installed that was not added to a
> > package I don't understand the ${PN}-dev here, and I'm not sure how
> > packaging works in this context - since it's not clear to me which files
> get
> > installed and which don't... except for when a recipe that depends on
> this
> > breaks because it can't find the header file.
>
> So you seem to have got yourself into a situation where the normal
> rules don't apply. Good luck!
>
-- 
Giordon Stark
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Bitbake recipe using CMake that requires python-six as part of compiling?

[Giordon Stark]

Hi Andre,

I tried without

FILES_${PN}_append = "${includedir}/open62541.h"

and got a QA error about a file installed that was not added to a
package I don't understand the ${PN}-dev here, and I'm not sure how
packaging works in this context - since it's not clear to me which files
get installed and which don't... except for when a recipe that depends on
this breaks because it can't find the header file.

Giordon

On Tue, Mar 6, 2018 at 4:06 PM Andre McCurdy <armccu...@gmail.com> wrote:

> On Tue, Mar 6, 2018 at 1:03 PM, Giordon Stark <kra...@gmail.com> wrote:
> > Yes. The CMakeLists file definitely doesn't install that (annoyingly).
> > Playing around a bit, I created a test recipe, added these lines in my
> > open62541.inc file (original recipe here)
> >
> > do_install_append() {
> >   install -d ${D}${includedir}
> >   install -m 644 ${B}/open62541.h ${D}${includedir}
> > }
> >
> > FILES_${PN}_append = "${includedir}/open62541.h"
>
> This is trying to put the header in the runtime package (ie the
> package containing files which typically end up in the target rootfs).
> Header files should be in the ${PN}-dev package instead.
>
> Since the default packaging rules already cover header files, you
> don't actually need to add anything here in order to have the header
> packaged correctly - just remove that line.
>
> Note that you also tried to use _append without a leading space -
> which is wrong in this context (it's wrong in almost every context).
>
> > and it looks like the test recipe can pick up that header file
> correctly. So
> > I think this is correct-er (at least for code that uses #include
> > ).
> >
>
-- 
Giordon Stark
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Bitbake recipe using CMake that requires python-six as part of compiling?

[Giordon Stark]

Yes. The CMakeLists file definitely doesn't install that (annoyingly).
Playing around a bit, I created a test recipe, added these lines in my
open62541.inc file (original recipe here)

do_install_append() {
  install -d ${D}${includedir}
  install -m 644 ${B}/open62541.h ${D}${includedir}
}

FILES_${PN}_append = "${includedir}/open62541.h"

and it looks like the test recipe can pick up that header file correctly.
So I think this is correct-er (at least for code that uses #include
).

Thanks for all the feedback so far,

Giordon

On Tue, Mar 6, 2018 at 3:00 PM Burton, Ross <ross.bur...@intel.com> wrote:

> If the cmakelists file doesn't install that (and it should) then yes
> you'll need to use do_install_append.
>
> Ross
>
> On 6 March 2018 at 20:46, Giordon Stark <kra...@gmail.com> wrote:
>
>> Great. So when I have this recipe set up -- how do I make sure, or tell
>> other people who write a recipe depending on this -- how to find a header
>> file built by it?
>>
>> Specifically, I see this header file in a (non-standard?) location which
>> is normally linked by others:
>>
>> |  #include 
>>
>> and this header file is at ${B}/open62541.h
>> (tmp/work/aarch64-poky-linux/open62541/0.3-r0/build/open62541.h). Is
>> this something that I just handle with a `do_install_append()` line? The
>> documentation here
>> https://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html isn't
>> very clear to me.
>>
>> e.g. for another recipe that just adds "open62541" in it's DEPENDS.
>>
>> Giordon
>>
>> On Tue, Mar 6, 2018 at 2:32 PM Burton, Ross <ross.bur...@intel.com>
>> wrote:
>>
>>> On 6 March 2018 at 20:24, Giordon Stark <kra...@gmail.com> wrote:
>>>
>>>> You can drop the S assignment as that is the default value.
>>>>>
>>>>
>>>> Didn't realize, neat. I knew I needed to set it for `git` clones since
>>>> it always throws it into a ${WORKDIR}/git folder.
>>>>
>>>
>>> Yes, for git clones you need to override it.
>>>
>>>
>>>>
>>>>> Github /archive/ tarballs can and do change over time, which gets very
>>>>> annoying when you need to go and change the checksums.
>>>>>
>>>>
>>>> Really? Dang...
>>>>
>>>
>>> Yeah. :/  Took us ages to verify this happens but it definitely does.
>>>
>>>
>>>> My hunch without reading the upstream CMake files is that they don't
>>>>> support out-of-tree builds.  If it worked from git then that's another
>>>>> reason to switch back.
>>>>>
>>>>
>>>> It seems like this is the case here. I'm ok using git clones for now.
>>>> Thanks.
>>>>
>>>
>>> It *shouldn't* matter here as the /archive/ tarball should have
>>> identical contents to a clone of the same tag, but it's possible that the
>>> build system looks for a .git/ directory and changes how it builds.  That's
>>> kind of stupid but it wouldn't be the first time I've seen it break builds.
>>>
>>> Ross
>>>
>> --
>> Giordon Stark
>>
>
> --
Giordon Stark
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Bitbake recipe using CMake that requires python-six as part of compiling?

[Giordon Stark]

Great. So when I have this recipe set up -- how do I make sure, or tell
other people who write a recipe depending on this -- how to find a header
file built by it?

Specifically, I see this header file in a (non-standard?) location which is
normally linked by others:

|  #include 

and this header file is at ${B}/open62541.h
(tmp/work/aarch64-poky-linux/open62541/0.3-r0/build/open62541.h). Is this
something that I just handle with a `do_install_append()` line? The
documentation here
https://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html isn't
very clear to me.

e.g. for another recipe that just adds "open62541" in it's DEPENDS.

Giordon

On Tue, Mar 6, 2018 at 2:32 PM Burton, Ross <ross.bur...@intel.com> wrote:

> On 6 March 2018 at 20:24, Giordon Stark <kra...@gmail.com> wrote:
>
>> You can drop the S assignment as that is the default value.
>>>
>>
>> Didn't realize, neat. I knew I needed to set it for `git` clones since it
>> always throws it into a ${WORKDIR}/git folder.
>>
>
> Yes, for git clones you need to override it.
>
>
>>
>>> Github /archive/ tarballs can and do change over time, which gets very
>>> annoying when you need to go and change the checksums.
>>>
>>
>> Really? Dang...
>>
>
> Yeah. :/  Took us ages to verify this happens but it definitely does.
>
>
>> My hunch without reading the upstream CMake files is that they don't
>>> support out-of-tree builds.  If it worked from git then that's another
>>> reason to switch back.
>>>
>>
>> It seems like this is the case here. I'm ok using git clones for now.
>> Thanks.
>>
>
> It *shouldn't* matter here as the /archive/ tarball should have identical
> contents to a clone of the same tag, but it's possible that the build
> system looks for a .git/ directory and changes how it builds.  That's kind
> of stupid but it wouldn't be the first time I've seen it break builds.
>
> Ross
>
-- 
Giordon Stark
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Bitbake recipe using CMake that requires python-six as part of compiling?

[Giordon Stark]

Thanks.

On Tue, Mar 6, 2018 at 2:07 PM Burton, Ross <ross.bur...@intel.com> wrote:

> On 6 March 2018 at 19:48, Giordon Stark <kra...@gmail.com> wrote:
>
>>
>> where PV=0.2 (open62541_0.2.bb). And I see an error on install (full
>> log: https://gist.github.com/kratsg/5c3740ab72403595d5b9e0e855a3697f)
>>
>> | CMake Error at cmake_install.cmake:40 (file):
>> |   file INSTALL cannot find
>> |
>>  
>> "/local/d4/gstark/poky/build/tmp/work/aarch64-poky-linux/open62541/0.2-r0/build/open62541.h".
>>
>> So I'm wondering if I screwed up something by using the tarball instead
>> of a clone. I thought I translated it relatively well, and the release
>> matches the hash I was using.
>>
>
> You can drop the S assignment as that is the default value.
>

Didn't realize, neat. I knew I needed to set it for `git` clones since it
always throws it into a ${WORKDIR}/git folder.


> Github /archive/ tarballs can and do change over time, which gets very
> annoying when you need to go and change the checksums.
>

Really? Dang...


>
> If open62541 don't provide proper tarballs then keep it doing a git clone
> of the sha of that tag.
>
> My hunch without reading the upstream CMake files is that they don't
> support out-of-tree builds.  If it worked from git then that's another
> reason to switch back.
>

It seems like this is the case here. I'm ok using git clones for now.
Thanks.


>
> Ross
>
-- 
Giordon Stark
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Bitbake recipe using CMake that requires python-six as part of compiling?

[Giordon Stark]

Thanks! Sorry to ping again, but I've done something poorly wrong. I
converted this code which now works, to point at the tarball provided by
github instead:

SUMMARY = "OPC UA implementation"
HOMEPAGE = "https://open62541.org/;
SECTION = "devel/libs"
LICENSE = "MPL-2.0"
LIC_FILES_CHKSUM = "file://LICENSE;md5=e879eaad64aab8e1f8e63e298f5cea28"
DEPENDS = "openssl python-six-native"

SRC_URI = "https://github.com/open62541/open62541/archive/v${PV}.tar.gz;
SRC_URI[md5sum] = "7c3fedab541e6df22de06c47cb4768fc"
SRC_URI[sha256sum] =
"2fc6eb2eca7d53db68206db7c9c7368f0a034992f050bee971e4823d3d739260"

S = "${WORKDIR}/${PN}-${PV}"

inherit cmake pythonnative

# Specify any options you want to pass to cmake using EXTRA_OECMAKE:
EXTRA_OECMAKE = "\
  -DCMAKE_BUILD_TYPE=Release \
"

FILES_${PN}_append = "\
  ${libdir}/cmake \
  ${libdir}/cmake/open62541*.cmake \
"

where PV=0.2 (open62541_0.2.bb). And I see an error on install (full log:
https://gist.github.com/kratsg/5c3740ab72403595d5b9e0e855a3697f)

| CMake Error at cmake_install.cmake:40 (file):
|   file INSTALL cannot find
|
 
"/local/d4/gstark/poky/build/tmp/work/aarch64-poky-linux/open62541/0.2-r0/build/open62541.h".

So I'm wondering if I screwed up something by using the tarball instead of
a clone. I thought I translated it relatively well, and the release matches
the hash I was using.

Giordon

On Tue, Mar 6, 2018 at 1:39 PM Philip Balister <phi...@balister.org> wrote:

> On 03/06/2018 02:14 PM, Giordon Stark wrote:
> > Hi Philip,
> >
> > That was it indeed! I've gotten it working. I don't see
> "python-six-native"
> > as a valid recipe in layers.openembedded.org. Is this a special case or
> is
> > there a way to identify these sorts of packages in the future?
>
> The python-six recipe should have a line like:
>
> BBCLASSEXTEND = "native"
>
> This tells bitbake it can build a native version by doing some tweaks to
> the toolchain it uses and where to put the output.
>
> Philip
>
>
> >
> > open62541-0.3+git999-r0 do_compile: NOTE: open62541: compiling from
> > external source tree
> /local/d4/gstark/poky/build/workspace/sources/open62541
> > ERROR: open62541-0.3+git999-r0 do_package: QA Issue: open62541:
> > Files/directories were installed but not shipped in any package:
> >   /usr/lib/cmake
> >   /usr/lib/cmake/open62541ConfigVersion.cmake
> >   /usr/lib/cmake/open62541Targets.cmake
> >   /usr/lib/cmake/open62541-config.cmake
> >   /usr/lib/cmake/open62541Targets-debug.cmake
> > Please set FILES such that these items are packaged. Alternatively if
> they
> > are unneeded, avoid installing them or delete them within do_install.
> > open62541: 5 installed and not shipped files. [installed-vs-shipped]
> > ERROR: open62541-0.3+git999-r0 do_package: Fatal QA errors found, failing
> > task.
> > ERROR: open62541-0.3+git999-r0 do_package: Function failed: do_package
> > ERROR: Logfile of failure stored in:
> >
> /local/d4/gstark/poky/build/tmp/work/aarch64-poky-linux/open62541/0.3+git999-r0/temp/log.do_package.14179
> > ERROR: Task
> >
> (/local/d4/gstark/poky/build/workspace/recipes/open62541/open62541_git.bb:
> do_package)
> > failed with exit code '1'
> > NOTE: Tasks Summary: Attempted 506 tasks of which 492 didn't need to be
> > rerun and 1 failed.
> >
> > Summary: 1 task failed:
> >   /local/d4/gstark/poky/build/workspace/recipes/open62541/
> open62541_git.bb:
> > do_package
> > Summary: There were 3 ERROR messages shown, returning a non-zero exit
> code.
> >
> >
> > I just need to remind myself of cleaning these files up :)
> >
> > Giordon
> >
> > On Tue, Mar 6, 2018 at 1:09 PM Philip Balister <phi...@balister.org>
> wrote:
> >
> >> On 03/06/2018 01:42 PM, Burton, Ross wrote:
> >>> Add DEPENDS=python-six
> >>
> >> Maybe:
> >>
> >> DEPENDS = "python-six-native"
> >>
> >> Philip
> >>
> >>>
> >>> Ross
> >>>
> >>> On 6 March 2018 at 18:11, Giordon Stark <kra...@gmail.com> wrote:
> >>>
> >>>> Hi all,
> >>>>
> >>>> I'm struggling with what should be a simple-ish recipe (I think). I'm
> >>>> writing a recipe implementation for
> >> https://github.com/open62541/open62541
> >>>>  (open62541). So I start with
> >>>>
> >>>> devtool add open62541 https://github.com/open62541/open62541.git
> >>>>
> >>>> then I edit this,

Re: [yocto] Bitbake recipe using CMake that requires python-six as part of compiling?

[Giordon Stark]

Hi Philip,

That was it indeed! I've gotten it working. I don't see "python-six-native"
as a valid recipe in layers.openembedded.org. Is this a special case or is
there a way to identify these sorts of packages in the future?

open62541-0.3+git999-r0 do_compile: NOTE: open62541: compiling from
external source tree /local/d4/gstark/poky/build/workspace/sources/open62541
ERROR: open62541-0.3+git999-r0 do_package: QA Issue: open62541:
Files/directories were installed but not shipped in any package:
  /usr/lib/cmake
  /usr/lib/cmake/open62541ConfigVersion.cmake
  /usr/lib/cmake/open62541Targets.cmake
  /usr/lib/cmake/open62541-config.cmake
  /usr/lib/cmake/open62541Targets-debug.cmake
Please set FILES such that these items are packaged. Alternatively if they
are unneeded, avoid installing them or delete them within do_install.
open62541: 5 installed and not shipped files. [installed-vs-shipped]
ERROR: open62541-0.3+git999-r0 do_package: Fatal QA errors found, failing
task.
ERROR: open62541-0.3+git999-r0 do_package: Function failed: do_package
ERROR: Logfile of failure stored in:
/local/d4/gstark/poky/build/tmp/work/aarch64-poky-linux/open62541/0.3+git999-r0/temp/log.do_package.14179
ERROR: Task
(/local/d4/gstark/poky/build/workspace/recipes/open62541/open62541_git.bb:do_package)
failed with exit code '1'
NOTE: Tasks Summary: Attempted 506 tasks of which 492 didn't need to be
rerun and 1 failed.

Summary: 1 task failed:
  /local/d4/gstark/poky/build/workspace/recipes/open62541/open62541_git.bb:
do_package
Summary: There were 3 ERROR messages shown, returning a non-zero exit code.


I just need to remind myself of cleaning these files up :)

Giordon

On Tue, Mar 6, 2018 at 1:09 PM Philip Balister <phi...@balister.org> wrote:

> On 03/06/2018 01:42 PM, Burton, Ross wrote:
> > Add DEPENDS=python-six
>
> Maybe:
>
> DEPENDS = "python-six-native"
>
> Philip
>
> >
> > Ross
> >
> > On 6 March 2018 at 18:11, Giordon Stark <kra...@gmail.com> wrote:
> >
> >> Hi all,
> >>
> >> I'm struggling with what should be a simple-ish recipe (I think). I'm
> >> writing a recipe implementation for
> https://github.com/open62541/open62541
> >>  (open62541). So I start with
> >>
> >> devtool add open62541 https://github.com/open62541/open62541.git
> >>
> >> then I edit this, so it currently looks like this for me:
> >>
> >> SUMMARY = "OPC UA implementation"
> >> LICENSE = "MPL-2.0"
> >> LIC_FILES_CHKSUM = "file://LICENSE;md5=815ca599c9df247a0c7f619bab123dad"
> >> SRC_URI = "gitsm://github.com/open62541/open62541.git;protocol=https"
> >> PV = "0.3+git${SRCPV}"
> >> SRCREV = "a6b99dc0579a53207b7dfe1d16423c2c1daa467e"
> >>
> >> S = "${WORKDIR}/git"
> >>
> >> # NOTE: unable to map the following CMake package dependencies: Check
> >> Sphinx ClangTools LATEX MbedTLS Valgrind
> >> DEPENDS = "openssl"
> >>
> >> inherit cmake pythonnative
> >>
> >> # Specify any options you want to pass to cmake using EXTRA_OECMAKE:
> >> EXTRA_OECMAKE = ""
> >>
> >> however, when I run devtool build open62541, I get  errors about "No
> >> module named six":
> >>
> >> | make[2]: Leaving directory '/local/d4/gstark/poky/build/
> >>
> tmp/work/aarch64-poky-linux/open62541/0.3+git999-r0/open62541-0.3+git999'
> >> | Traceback (most recent call last):
> >> |   File "/local/d4/gstark/poky/build/workspace/sources/open62541/
> >> tools/nodeset_compiler/nodeset_compiler.py", line 27, in 
> >> | from nodeset import *
> >> |   File "/local/d4/gstark/poky/build/workspace/sources/open62541/
> >> tools/nodeset_compiler/nodeset.py", line 30, in 
> >> | from nodes import *
> >> |   File "/local/d4/gstark/poky/build/workspace/sources/open62541/
> >> tools/nodeset_compiler/nodes.py", line 21, in 
> >> | from datatypes import *
> >> |   File "/local/d4/gstark/poky/build/workspace/sources/open62541/
> >> tools/nodeset_compiler/datatypes.py", line 29, in 
> >> | import six
> >> | ImportError: No module named six
> >> | CMakeFiles/open62541-generator-namespace.dir/build.make:71: recipe for
> >> target 'src_generated/ua_namespace0.c' failed
> >> | make[2]: *** [src_generated/ua_namespace0.c] Error 1
> >> | make[2]: Leaving directory '/local/d4/gstark/poky/build/
> >>
> tmp/work/aarch64-poky-linux/open62541/0.3+git999-r0/open62541-0.3+git999'
> >> | CMakeFiles/Makefile2:108: recipe for target
> 'CMakeFiles/open62541-generator-namespace.dir/all'
> >> failed
> >> | make[1]: *** [CMakeFiles/open62541-generator-namespace.dir/all] Error
> 2
> >> | make[1]: *** Waiting for unfinished jobs
> >>
> >> How do I get "python-six" added as part of pythonnative?
> >>
> >> Giordon
> >>
> >> --
> >> Giordon Stark
> >>
> >> --
> >> ___
> >> yocto mailing list
> >> yocto@yoctoproject.org
> >> https://lists.yoctoproject.org/listinfo/yocto
> >>
> >>
> >
> >
> >
>
-- 
Giordon Stark
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Bitbake recipe using CMake that requires python-six as part of compiling?

[Giordon Stark]

More specifically, the problem is that "six" is not a package that was
installed as part of pythonnative:

kratsg@dc:/local/d4/gstark/poky/build$
/local/d4/gstark/poky/build/tmp/work/aarch64-poky-linux/open62541/0.3+git999-r0/recipe-sysroot-native/usr/bin/python-native/python
Python 2.7.13 (default, Jan  3 2018, 08:10:02)
[GCC 5.4.0 20160609] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import six
Traceback (most recent call last):
  File "", line 1, in 
ImportError: No module named six
>>> import sys
>>> sys.path
['', '/users/kratsg/L1TriggerAnalysis/.local/lib/python2.6/site-packages',
'/local/d4/gstark/poky/build',
'/local/d4/gstark/poky/build/tmp/work/aarch64-poky-linux/open62541/0.3+git999-r0/recipe-sysroot-native/usr/lib/python27.zip',
'/local/d4/gstark/poky/build/tmp/work/aarch64-poky-linux/open62541/0.3+git999-r0/recipe-sysroot-native/usr/lib/python2.7',
'/local/d4/gstark/poky/build/tmp/work/aarch64-poky-linux/open62541/0.3+git999-r0/recipe-sysroot-native/usr/lib/python2.7/plat-linux2',
'/local/d4/gstark/poky/build/tmp/work/aarch64-poky-linux/open62541/0.3+git999-r0/recipe-sysroot-native/usr/lib/python2.7/lib-tk',
'/local/d4/gstark/poky/build/tmp/work/aarch64-poky-linux/open62541/0.3+git999-r0/recipe-sysroot-native/usr/lib/python2.7/lib-old',
'/local/d4/gstark/poky/build/tmp/work/aarch64-poky-linux/open62541/0.3+git999-r0/recipe-sysroot-native/usr/lib/python2.7/lib-dynload',
'/local/d4/gstark/poky/build/tmp/work/aarch64-poky-linux/open62541/0.3+git999-r0/recipe-sysroot-native/usr/lib/python2.7/site-packages']

And I have a hard time googling/searching to figure out how to solve this
since most answers are about installing python packages on a target
machine, rather than for the host's pythonnative.

Giordon


On Tue, Mar 6, 2018 at 12:50 PM Giordon Stark <kra...@gmail.com> wrote:

> Hi,
>
> I tried this and it didn't work.
>
> Giordon
> On Tue, Mar 6, 2018 at 12:43 Burton, Ross <ross.bur...@intel.com> wrote:
>
>> Add DEPENDS=python-six
>>
>> Ross
>>
>> On 6 March 2018 at 18:11, Giordon Stark <kra...@gmail.com> wrote:
>>
>>> Hi all,
>>>
>>> I'm struggling with what should be a simple-ish recipe (I think). I'm
>>> writing a recipe implementation for
>>> https://github.com/open62541/open62541 (open62541). So I start with
>>>
>>> devtool add open62541 https://github.com/open62541/open62541.git
>>>
>>> then I edit this, so it currently looks like this for me:
>>>
>>> SUMMARY = "OPC UA implementation"
>>> LICENSE = "MPL-2.0"
>>> LIC_FILES_CHKSUM = "file://LICENSE;md5=815ca599c9df247a0c7f619bab123dad"
>>> SRC_URI = "gitsm://github.com/open62541/open62541.git;protocol=https"
>>> PV = "0.3+git${SRCPV}"
>>> SRCREV = "a6b99dc0579a53207b7dfe1d16423c2c1daa467e"
>>>
>>> S = "${WORKDIR}/git"
>>>
>>> # NOTE: unable to map the following CMake package dependencies: Check
>>> Sphinx ClangTools LATEX MbedTLS Valgrind
>>> DEPENDS = "openssl"
>>>
>>> inherit cmake pythonnative
>>>
>>> # Specify any options you want to pass to cmake using EXTRA_OECMAKE:
>>> EXTRA_OECMAKE = ""
>>>
>>> however, when I run devtool build open62541, I get  errors about "No
>>> module named six":
>>>
>>> | make[2]: Leaving directory
>>> '/local/d4/gstark/poky/build/tmp/work/aarch64-poky-linux/open62541/0.3+git999-r0/open62541-0.3+git999'
>>> | Traceback (most recent call last):
>>> |   File
>>> "/local/d4/gstark/poky/build/workspace/sources/open62541/tools/nodeset_compiler/nodeset_compiler.py",
>>> line 27, in 
>>> | from nodeset import *
>>> |   File
>>> "/local/d4/gstark/poky/build/workspace/sources/open62541/tools/nodeset_compiler/nodeset.py",
>>> line 30, in 
>>> | from nodes import *
>>> |   File
>>> "/local/d4/gstark/poky/build/workspace/sources/open62541/tools/nodeset_compiler/nodes.py",
>>> line 21, in 
>>> | from datatypes import *
>>> |   File
>>> "/local/d4/gstark/poky/build/workspace/sources/open62541/tools/nodeset_compiler/datatypes.py",
>>> line 29, in 
>>> | import six
>>> | ImportError: No module named six
>>> | CMakeFiles/open62541-generator-namespace.dir/build.make:71: recipe for
>>> target 'src_generated/ua_namespace0.c' failed
>>> | make[2]: *** [src_generated/ua_namespace0.c] Error 1
>&g

Re: [yocto] Bitbake recipe using CMake that requires python-six as part of compiling?

[Giordon Stark]

Hi,

I tried this and it didn't work.

Giordon
On Tue, Mar 6, 2018 at 12:43 Burton, Ross <ross.bur...@intel.com> wrote:

> Add DEPENDS=python-six
>
> Ross
>
> On 6 March 2018 at 18:11, Giordon Stark <kra...@gmail.com> wrote:
>
>> Hi all,
>>
>> I'm struggling with what should be a simple-ish recipe (I think). I'm
>> writing a recipe implementation for
>> https://github.com/open62541/open62541 (open62541). So I start with
>>
>> devtool add open62541 https://github.com/open62541/open62541.git
>>
>> then I edit this, so it currently looks like this for me:
>>
>> SUMMARY = "OPC UA implementation"
>> LICENSE = "MPL-2.0"
>> LIC_FILES_CHKSUM = "file://LICENSE;md5=815ca599c9df247a0c7f619bab123dad"
>> SRC_URI = "gitsm://github.com/open62541/open62541.git;protocol=https"
>> PV = "0.3+git${SRCPV}"
>> SRCREV = "a6b99dc0579a53207b7dfe1d16423c2c1daa467e"
>>
>> S = "${WORKDIR}/git"
>>
>> # NOTE: unable to map the following CMake package dependencies: Check
>> Sphinx ClangTools LATEX MbedTLS Valgrind
>> DEPENDS = "openssl"
>>
>> inherit cmake pythonnative
>>
>> # Specify any options you want to pass to cmake using EXTRA_OECMAKE:
>> EXTRA_OECMAKE = ""
>>
>> however, when I run devtool build open62541, I get  errors about "No
>> module named six":
>>
>> | make[2]: Leaving directory
>> '/local/d4/gstark/poky/build/tmp/work/aarch64-poky-linux/open62541/0.3+git999-r0/open62541-0.3+git999'
>> | Traceback (most recent call last):
>> |   File
>> "/local/d4/gstark/poky/build/workspace/sources/open62541/tools/nodeset_compiler/nodeset_compiler.py",
>> line 27, in 
>> | from nodeset import *
>> |   File
>> "/local/d4/gstark/poky/build/workspace/sources/open62541/tools/nodeset_compiler/nodeset.py",
>> line 30, in 
>> | from nodes import *
>> |   File
>> "/local/d4/gstark/poky/build/workspace/sources/open62541/tools/nodeset_compiler/nodes.py",
>> line 21, in 
>> | from datatypes import *
>> |   File
>> "/local/d4/gstark/poky/build/workspace/sources/open62541/tools/nodeset_compiler/datatypes.py",
>> line 29, in 
>> | import six
>> | ImportError: No module named six
>> | CMakeFiles/open62541-generator-namespace.dir/build.make:71: recipe for
>> target 'src_generated/ua_namespace0.c' failed
>> | make[2]: *** [src_generated/ua_namespace0.c] Error 1
>> | make[2]: Leaving directory
>> '/local/d4/gstark/poky/build/tmp/work/aarch64-poky-linux/open62541/0.3+git999-r0/open62541-0.3+git999'
>> | CMakeFiles/Makefile2:108: recipe for target
>> 'CMakeFiles/open62541-generator-namespace.dir/all' failed
>> | make[1]: *** [CMakeFiles/open62541-generator-namespace.dir/all] Error 2
>> | make[1]: *** Waiting for unfinished jobs
>>
>> How do I get "python-six" added as part of pythonnative?
>>
>> Giordon
>>
>> --
>> Giordon Stark
>>
>> --
>> ___
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>> --
Giordon Stark
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Bitbake recipe using CMake that requires python-six as part of compiling?

[Giordon Stark]

Hi all,

I'm struggling with what should be a simple-ish recipe (I think). I'm
writing a recipe implementation for
https://github.com/open62541/open62541 (open62541).
So I start with

devtool add open62541 https://github.com/open62541/open62541.git

then I edit this, so it currently looks like this for me:

SUMMARY = "OPC UA implementation"
LICENSE = "MPL-2.0"
LIC_FILES_CHKSUM = "file://LICENSE;md5=815ca599c9df247a0c7f619bab123dad"
SRC_URI = "gitsm://github.com/open62541/open62541.git;protocol=https"
PV = "0.3+git${SRCPV}"
SRCREV = "a6b99dc0579a53207b7dfe1d16423c2c1daa467e"

S = "${WORKDIR}/git"

# NOTE: unable to map the following CMake package dependencies: Check
Sphinx ClangTools LATEX MbedTLS Valgrind
DEPENDS = "openssl"

inherit cmake pythonnative

# Specify any options you want to pass to cmake using EXTRA_OECMAKE:
EXTRA_OECMAKE = ""

however, when I run devtool build open62541, I get  errors about "No module
named six":

| make[2]: Leaving directory
'/local/d4/gstark/poky/build/tmp/work/aarch64-poky-linux/open62541/0.3+git999-r0/open62541-0.3+git999'
| Traceback (most recent call last):
|   File
"/local/d4/gstark/poky/build/workspace/sources/open62541/tools/nodeset_compiler/nodeset_compiler.py",
line 27, in 
| from nodeset import *
|   File
"/local/d4/gstark/poky/build/workspace/sources/open62541/tools/nodeset_compiler/nodeset.py",
line 30, in 
| from nodes import *
|   File
"/local/d4/gstark/poky/build/workspace/sources/open62541/tools/nodeset_compiler/nodes.py",
line 21, in 
| from datatypes import *
|   File
"/local/d4/gstark/poky/build/workspace/sources/open62541/tools/nodeset_compiler/datatypes.py",
line 29, in 
| import six
| ImportError: No module named six
| CMakeFiles/open62541-generator-namespace.dir/build.make:71: recipe for
target 'src_generated/ua_namespace0.c' failed
| make[2]: *** [src_generated/ua_namespace0.c] Error 1
| make[2]: Leaving directory
'/local/d4/gstark/poky/build/tmp/work/aarch64-poky-linux/open62541/0.3+git999-r0/open62541-0.3+git999'
| CMakeFiles/Makefile2:108: recipe for target
'CMakeFiles/open62541-generator-namespace.dir/all' failed
| make[1]: *** [CMakeFiles/open62541-generator-namespace.dir/all] Error 2
| make[1]: *** Waiting for unfinished jobs

How do I get "python-six" added as part of pythonnative?

Giordon

-- 
Giordon Stark
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Adding custom scripts to home directory and /etc/init.d/*

[Giordon Stark]

Thanks Anuj,

This is where I ended up for now (let me know if this looks about right):

# see https://stackoverflow.com/a/40768781
DESCRIPTION = "Clock Configuration via I2C"
SRC_URI = "file://init-clock"
LICENSE = "MIT"
LIC_FILES_CHKSUM =
"file://${WORKDIR}/init-clock;beginline=2;endline=19;md5=846eef20187f1d9f7f2af0d254faa171"

# these 3 lines will have the script run on boot
inherit update-rc.d
INITSCRIPT_PACKAGES = "${PN}"
INITSCRIPT_NAME = "init-clock"

# install it in the correct location for update-rc.d
do_install() {
  install -d ${D}${INIT_D_DIR}
  install -m 0755 ${WORKDIR}/init-clock ${D}${INIT_D_DIR}/init-clock
}

*# package it as it is not installed in a standard location*
*FILES_${PN} = "${INIT_D_DIR}/init-clock"*

The one thing I'm not 100% sure I understand is the last line that I
bolded, but it seems to be needed.

Thanks,

Giordon

On Mon, Mar 5, 2018 at 6:36 PM Anuj Mittal <anuj.mit...@intel.com> wrote:

> On 03/06/2018 05:18 AM, Giordon Stark wrote:
> > Hi all,
> >
> > I am wondering if there's a nice pattern or workflow within Yocto where
> > I can add a custom shell script to /etc/init.d for the purposes of
> > running it on OS boot (which also requires running update.rc I believe)
>
> You can inherit update-rc.d class and define INITSCRIPT_NAME/PARAMS in
> your recipe.
>
>
> https://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#ref-classes-update-rc.d
>
> > as well as prepopulating the home directory with some files of my
> choosing.
> >
> > If someone could point me in the right direction, that would be great!
> >
> > Giordon
> > --
> > Giordon Stark
> >
> >
>
> --
Giordon Stark
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Adding custom scripts to home directory and /etc/init.d/*

[Giordon Stark]

Hi all,

I am wondering if there's a nice pattern or workflow within Yocto where I
can add a custom shell script to /etc/init.d for the purposes of running it
on OS boot (which also requires running update.rc I believe) as well as
prepopulating the home directory with some files of my choosing.

If someone could point me in the right direction, that would be great!

Giordon
-- 
Giordon Stark
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Read Only File System

[Giordon Stark]

Hi Jose,

I don't know if you're using a custom device tree or not, but I ran into
this issue and solved it by disabling write protection in the device tree:

https://github.com/kratsg/meta-l1calo/blob/master/recipes-bsp/device-tree/files/gfex-prototype4/gfex-prototype4.dts#L48-L51


 {
  disable-wp;
};

Giordon

On Sun, Mar 4, 2018 at 8:20 PM Jose David Bravo Alvarez <
josedavidbr...@hotmail.com> wrote:

> I'm building a image using Yocto rocky and Xilinx for my zynq-702 board.
>
>
> But for some reason my root file system can only be mounted as a read
> only. If I put rw in the u-boot load command it fails. I'm booting from a
> SD card, that doesn't have any lock switch.
>
>
> And if I boot using other kernel different than the one generated by yocto
> it does mount the file system as read write... the problem is somewhere in
> my image and not physical in the SD card or in the controller.
>
>
> If generate my yocto image using a qemux86 machine, it does work good and
> mount the partition as rw.
>
>
> This is the latest part of my boot log:
>
> Waiting for root device /dev/mmcblk0p2...
>
> mmc0: new high speed SDHC card at address 
>
> mmcblk0: mmc0: SL08G 7.40 GiB (ro)
>
>  mmcblk0: p1 p2
>
> VFS: Cannot open root device "mmcblk0p2" or unknown-block(179,2): error
> -30
> Please append a correct "root=" boot option; here are the available
> partitions:
> 0100   16384 ram0  (driver?)
>
> 0101   16384 ram1  (driver?)
>
> 0102   16384 ram2  (driver?)
>
> 0103   16384 ram3  (driver?)
>
> 0104   16384 ram4  (driver?)
>
> 0105   16384 ram5  (driver?)
>
> 0106   16384 ram6  (driver?)
>
> 0107   16384 ram7  (driver?)
>
> 0108   16384 ram8  (driver?)
>
> 0109   16384 ram9  (driver?)
>
> 010a   16384 ram10  (driver?)
>
> 010b   16384 ram11  (driver?)
>
> 010c   16384 ram12  (driver?)
>
> 010d   16384 ram13  (driver?)
>
> 010e   16384 ram14  (driver?)
>
> 010f   16384 ram15  (driver?)
>
> b300 7761920 mmcblk0  driver: mmcblk
>
>   b301 1048576 mmcblk0p1 9d7a9d10-01
>
>   b302 6712320 mmcblk0p2 9d7a9d10-02
>
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(179,2)
> CPU1: stopping
>
> CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.9.0-xilinx-v2017.3 #1
>
> Hardware name: Xilinx Zynq Platform
>
> [] (unwind_backtrace) from [] (show_stack+0x10/0x14)
>
> [] (show_stack) from [] (dump_stack+0x80/0xa0)
>
> [] (dump_stack) from [] (ipi_cpu_stop+0x3c/0x70)
>
> [] (ipi_cpu_stop) from [] (handle_IPI+0x64/0x84)
>
> [] (handle_IPI) from [] (gic_handle_irq+0x80/0x8c)
>
> [] (gic_handle_irq) from [] (__irq_svc+0x6c/0xa8)
>
> Exception stack(0xde471f70 to 0xde471fb8)
>
> 1f60:   1e29c000
> debde9c0
> 1f80: 49d2e7a1  debdde40 0001 47add66a  
> 0001
> 1fa0: 0015 de471fc0 c04af5dc c04af600 6013 
>
> [] (__irq_svc) from []
> (cpuidle_enter_state+0xe4/0x1b4)
> [] (cpuidle_enter_state) from []
> (cpu_startup_entry+0x18c/0)
> [] (cpu_startup_entry) from [<001014cc>] (0x1014cc)
>
> ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-bl)
>
> Thanks for your help!
>
>
> Jose Bravo
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
Giordon Stark
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Creating a python recipe with devtool

[Giordon Stark]

This also works with the tarball URLs from pypi which is a bit easier to
manage (version-wise).

Giordon

On Wed, Feb 7, 2018 at 7:10 AM Alan Martinovic <alan.martino...@senic.com>
wrote:

> Thanks, that worked!
>
> Steps:
>
> # On the build server
> devtool create-workspace
> devtool add  https://github.com/jruere/multiprocessing-logging
> devtool
> devtool edit-recipe multiprocessing-logging
> # Change for building for python3
>inherit setuptools -> inherit setuptools3
> # delete the RDEPENDS that were wrongly detected
> devtool build multiprocessing-logging
> #Prerequisit: ssh root@10.10.10.100
> devtool deploy-target multiprocessing-logging root@10.10.10.100
>
> #On the 10.10.10.100 device
> python3
> import python3-multiprocessing_logging
>
> #On the build server. Finishing
> devtool finish multiprocessing-logging
> /home/alan/meta-myproject/recipes-devtools/python
>
> On Wed, Feb 7, 2018 at 1:25 PM, Alexander Kanavin
> <alexander.kana...@linux.intel.com> wrote:
> > On 02/07/2018 02:17 PM, Alan Martinovic wrote:
> >>
> >>  devtool add
> >>
> >>
> https://pypi.python.org/packages/65/eb/1c3db9596eddb2bd1d1f8153dcaf2d9f2c7e144f4832d1b1449f681a0a7a/multiprocessing_logging-0.2.6-py2.py3-none-any.whl#md5=b7783a8c449135e5bb344b3f0caa3522
> >
> >
> > I don't think we support .whl format at the moment. You need to fetch
> > sources directly from github.
> >
> >
> > Alex
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
Giordon Stark
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] recipe for custom python package not on pypi

[Giordon Stark]

Hi,

https://github.com/kratsg/meta-l1calo/blob/master/recipes-core/python/python-ironman_0.2.13.bb
-
this is an example recipe for python.

You simply need to change the SRC_URI to point to where your python package
is (tarball generally preferred) by something like

file://path/to/tarball.tar.gz

Giordon

On Wed, Jan 3, 2018 at 6:39 PM Matt Schepers 
wrote:

> Folks,
>
> I'm looking for a recipe that will install a custom python package to the
> python site-packages on the rootfs. The Python package uses setuptools and
> the standard setup.py and is not available on pypi because I wrote it. In
> general I am having difficulty finding a recipe for a custom package
> outside of the ones available on pypi.
>
> Can someone point me in the right direction?
>
> Thanks,
> Matt
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Machine definition ?

[Giordon Stark]

Hi,

You should be able to write

MACHINE = "orange-pi-one"

to set the machine correctly.

Giordon

On Wed, Aug 16, 2017 at 10:23 PM Riko  wrote:

> Dear Yocto Members,
>
> I have a question related with machine,
>
> If I want to use Orange Pi, how can I define my machine on local.conf ?
>
> Related with :
>
> https://github.com/linux-sunxi/meta-sunxi/tree/morty/conf/machine
>
>
> /*
>
> Sent By
>
> Ubuntu 16.04 LTS
>
> Regards,
>
> Riko H
>
> */
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] LLVM linking for custom recipe

[Giordon Stark]

Hi,

I'm still stuck here, assistance would be appreciated.

Giordon

On Thu, Jun 8, 2017 at 7:51 PM Giordon Stark <kra...@gmail.com> wrote:

> Looking into more details, I don't know or where bitbake tries to look for
> things as things get compiled (flags, environment, etc)... but the error
> message does say ROOT is looking for
>
> LLVMConfig.cmake
> llvm-config.cmake
>
> However, I see
>
>
> tmp/work/aarch64-poky-linux/llvm3.3/3.3-r0/llvm-3.3.src/cmake/modules/LLVM-Config.cmake
>
> which is perhaps why it can't find it. I assume the output name here isn't
> 100% compatible, and I'm using meta-oe's llvm3.3. I'm just mostly stuck on
> CMake's default behavior here, I think.
>
> Giordon
>
> On Thu, Jun 8, 2017 at 4:37 PM Giordon Stark <kra...@gmail.com> wrote:
>
>> Hi Khem,
>>
>> Which recipe? My problem is that ROOT's CMake is unable to find the
>> cross-compiled LLVM, and I'm not sure how to get it to find it.
>>
>> Giordon
>>
>> On Thu, Jun 8, 2017 at 3:47 PM Khem Raj <raj.k...@gmail.com> wrote:
>>
>>> On Thu, Jun 8, 2017 at 1:42 PM, Giordon Stark <kra...@gmail.com> wrote:
>>> > Hi,
>>> >
>>> > I have the following error message when trying to get LLVM linked up.
>>> The
>>> > problem is that I'm using a widely used science software called ROOT
>>> > (https://root.cern.ch/) with the following minimal recipe at the
>>> moment
>>> > (
>>> https://github.com/kratsg/meta-l1calo/blob/master/recipes-core/root/root_6.04.12.bb
>>> )
>>> > however I get the following error...
>>> >
>>> > Any ideas?
>>>
>>> Look into meta-clang there are patches for cross compiling clang/llvm
>>> https://github.com/kraj/meta-clang
>>>
>>> >
>>> > Giordon
>>> >
>>> > | CMake Error at cmake/modules/SearchInstalledSoftware.cmake:662
>>> > (find_package):
>>> > |   By not providing "FindLLVM.cmake" in CMAKE_MODULE_PATH this
>>> project has
>>> > |   asked CMake to find a package configuration file provided by
>>> "LLVM", but
>>> > |   CMake did not find one.
>>> > |
>>> > |   Could not find a package configuration file provided by "LLVM"
>>> with any
>>> > of
>>> > |   the following names:
>>> > |
>>> > | LLVMConfig.cmake
>>> > | llvm-config.cmake
>>> > |
>>> > |   Add the installation prefix of "LLVM" to CMAKE_PREFIX_PATH or set
>>> > |   "LLVM_DIR" to a directory containing one of the above files.  If
>>> "LLVM"
>>> > |   provides a separate development package or SDK, be sure it has been
>>> > |   installed.
>>> > | Call Stack (most recent call first):
>>> > |   CMakeLists.txt:58 (include)
>>> > |
>>> > |
>>> > | -- Configuring incomplete, errors occurred!
>>> > | See also
>>> >
>>> "/local/d4/poky/build/tmp/work/aarch64-poky-linux/root/6.04.12-r0/build/CMakeFiles/CMakeOutput.log".
>>> > | See also
>>> >
>>> "/local/d4/poky/build/tmp/work/aarch64-poky-linux/root/6.04.12-r0/build/CMakeFiles/CMakeError.log".
>>> > | WARNING:
>>> >
>>> /local/d4/poky/build/tmp/work/aarch64-poky-linux/root/6.04.12-r0/temp/run.do_configure.16761:1
>>> > exit 1 from 'cmake ${OECMAKE_SITEFILE}
>>> >
>>> /local/d4/poky/build/tmp/work/aarch64-poky-linux/root/6.04.12-r0/root-6.04.12
>>> > -DCMAKE_INSTALL_PREFIX:PATH=/usr -DCMAKE_INSTALL_BINDIR:PATH=bin
>>> > -DCMAKE_INSTALL_SBINDIR:PATH=sbin
>>> -DCMAKE_INSTALL_LIBEXECDIR:PATH=libexec
>>> > -DCMAKE_INSTALL_SYSCONFDIR:PATH=/etc
>>> > -DCMAKE_INSTALL_SHAREDSTATEDIR:PATH=../com
>>> > -DCMAKE_INSTALL_LOCALSTATEDIR:PATH=/var -DCMAKE_INSTALL_LIBDIR:PATH=lib
>>> > -DCMAKE_INSTALL_INCLUDEDIR:PATH=include
>>> > -DCMAKE_INSTALL_DATAROOTDIR:PATH=share -DCMAKE_INSTALL_SO_NO_EXE=0
>>> >
>>> -DCMAKE_TOOLCHAIN_FILE=/local/d4/poky/build/tmp/work/aarch64-poky-linux/root/6.04.12-r0/toolchain.cmake
>>> > -DCMAKE_VERBOSE_MAKEFILE=1 -DCMAKE_NO_SYSTEM_FROM_IMPORTED=1
>>> -Drootfit=ON
>>> > -Dminuit2=ON -Dpython=ON -Dssl=ON -Dxrootd=ON -Dbuiltin_freetype=ON
>>> > -Dbuiltin_llvm=OFF ${PACKAGECONFIG_CONFARGS} -Wno-dev'
>>> > | ERROR: Function failed: do_configure (log file is located at
>>> >
>>> /local/d4/poky/build/tmp/work/aarch64-poky-linux/root/6.04.12-r0/temp/log.do_configure.16761)
>>> > ERROR: Task
>>> > (/local/d4/meta-l1calo/recipes-core/root/root_6.04.12.bb:do_configure)
>>> > failed with exit code '1'
>>> > NOTE: Tasks Summary: Attempted 1027 tasks of which 1024 didn't need to
>>> be
>>> > rerun and 1 failed.
>>> >
>>> > Summary: 1 task failed:
>>> >   /local/d4/meta-l1calo/recipes-core/root/root_6.04.12.bb:do_configure
>>> > Summary: There was 1 ERROR message shown, returning a non-zero exit
>>> code.
>>> >
>>> >
>>> > --
>>> > ___
>>> > yocto mailing list
>>> > yocto@yoctoproject.org
>>> > https://lists.yoctoproject.org/listinfo/yocto
>>> >
>>>
>>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] LLVM linking for custom recipe

[Giordon Stark]

Hi,

I have the following error message when trying to get LLVM linked up. The
problem is that I'm using a widely used science software called ROOT (
https://root.cern.ch/) with the following minimal recipe at the moment (
https://github.com/kratsg/meta-l1calo/blob/master/recipes-core/root/root_6.04.12.bb)
however I get the following error...

Any ideas?

Giordon

| CMake Error at cmake/modules/SearchInstalledSoftware.cmake:662
(find_package):
|   By not providing "FindLLVM.cmake" in CMAKE_MODULE_PATH this project has
|   asked CMake to find a package configuration file provided by "LLVM", but
|   CMake did not find one.
|
|   Could not find a package configuration file provided by "LLVM" with any
of
|   the following names:
|
| LLVMConfig.cmake
| llvm-config.cmake
|
|   Add the installation prefix of "LLVM" to CMAKE_PREFIX_PATH or set
|   "LLVM_DIR" to a directory containing one of the above files.  If "LLVM"
|   provides a separate development package or SDK, be sure it has been
|   installed.
| Call Stack (most recent call first):
|   CMakeLists.txt:58 (include)
|
|
| -- Configuring incomplete, errors occurred!
| See also
"/local/d4/poky/build/tmp/work/aarch64-poky-linux/root/6.04.12-r0/build/CMakeFiles/CMakeOutput.log".
| See also
"/local/d4/poky/build/tmp/work/aarch64-poky-linux/root/6.04.12-r0/build/CMakeFiles/CMakeError.log".
| WARNING:
/local/d4/poky/build/tmp/work/aarch64-poky-linux/root/6.04.12-r0/temp/run.do_configure.16761:1
exit 1 from 'cmake ${OECMAKE_SITEFILE}
/local/d4/poky/build/tmp/work/aarch64-poky-linux/root/6.04.12-r0/root-6.04.12
-DCMAKE_INSTALL_PREFIX:PATH=/usr -DCMAKE_INSTALL_BINDIR:PATH=bin
-DCMAKE_INSTALL_SBINDIR:PATH=sbin -DCMAKE_INSTALL_LIBEXECDIR:PATH=libexec
-DCMAKE_INSTALL_SYSCONFDIR:PATH=/etc
-DCMAKE_INSTALL_SHAREDSTATEDIR:PATH=../com
-DCMAKE_INSTALL_LOCALSTATEDIR:PATH=/var -DCMAKE_INSTALL_LIBDIR:PATH=lib
-DCMAKE_INSTALL_INCLUDEDIR:PATH=include
-DCMAKE_INSTALL_DATAROOTDIR:PATH=share -DCMAKE_INSTALL_SO_NO_EXE=0
-DCMAKE_TOOLCHAIN_FILE=/local/d4/poky/build/tmp/work/aarch64-poky-linux/root/6.04.12-r0/toolchain.cmake
-DCMAKE_VERBOSE_MAKEFILE=1 -DCMAKE_NO_SYSTEM_FROM_IMPORTED=1 -Drootfit=ON
-Dminuit2=ON -Dpython=ON -Dssl=ON -Dxrootd=ON -Dbuiltin_freetype=ON
-Dbuiltin_llvm=OFF ${PACKAGECONFIG_CONFARGS} -Wno-dev'
| ERROR: Function failed: do_configure (log file is located at
/local/d4/poky/build/tmp/work/aarch64-poky-linux/root/6.04.12-r0/temp/log.do_configure.16761)
ERROR: Task 
(/local/d4/meta-l1calo/recipes-core/root/root_6.04.12.bb:do_configure)
failed with exit code '1'
NOTE: Tasks Summary: Attempted 1027 tasks of which 1024 didn't need to be
rerun and 1 failed.

Summary: 1 task failed:
  /local/d4/meta-l1calo/recipes-core/root/root_6.04.12.bb:do_configure
Summary: There was 1 ERROR message shown, returning a non-zero exit code.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [Openembedded-architecture] Standalone image writer

[Giordon Stark]

Hi all,

In a similar problem -- I find that the boot.bin file does not work out of
the box when I copy the files over to the SDCard to boot on a Xilinx board.
I end up having to open the SDK and generate a BOOT image myself using the
other files that were generated (u-boot, devicetree) with the SDK's
FSBL.elf. Is this a known problem or would a centralized solution for
creating the image solve this?

Giordon

On Mon, Feb 29, 2016 at 1:53 PM Paul Eggleton 
wrote:

> On Mon, 29 Feb 2016 11:27:15 Barros Pena, Belen wrote:
> > On 29/02/2016 08:12, "yocto-boun...@yoctoproject.org on behalf of Paul
> > Eggleton"  > paul.eggle...@linux.intel.com> wrote:
> > >There isn't a frontend UI for wic that I am aware of though - as I
> > >mentioned earlier image-writer has no support for it, it's just doing a
> > >straight dd to the device.
> >
> > We would really like to add support for wic at some point.
> >
> > https://bugzilla.yoctoproject.org/show_bug.cgi?id=8769
>
> True, but that's a slightly different usage of wic - i.e. preparing the
> formatted image, which we should support. However, writing a formatted
> image
> to an SD card / USB stick isn't something you could practically do from a
> web-
> based application I don't think - not without help from a local
> application at
> any rate.
>
> Cheers,
> Paul
>
> --
>
> Paul Eggleton
> Intel Open Source Technology Centre
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Trying to add a recipe for ROOT

[Giordon Stark]

Ping - any updates on this? I've tried a lot of ways to fix it, but I can't
seem to get it to compile at all...

On Wed, Dec 30, 2015 at 3:28 PM Giordon Stark <kra...@gmail.com> wrote:

> Here's an update set of logs:
>
> (output) https://gist.github.com/anonymous/56f904b65feeb3346db6
> (CMakeError.log) https://gist.github.com/anonymous/d5d766badcee1df5efc1
>
> for the current recipe here:
> https://github.com/kratsg/meta-l1calo/blob/master/recipes-core/root/root_6.04.12.bb
>
> On Wed, Dec 30, 2015 at 2:10 PM Giordon Stark <kra...@gmail.com> wrote:
>
>> Actually -- if you look here -- I'm already using pkg-config?
>>
>>
>> https://github.com/kratsg/meta-l1calo/blob/master/recipes-core/root/root_6.04.12.bb#L9
>>
>> Is there something wrong with the configuration then?
>>
>> On Wed, Dec 30, 2015 at 2:07 PM Giordon Stark <kra...@gmail.com> wrote:
>>
>>> I'm unable to disable the internal build. I'm working on the pkg-config
>>> however.
>>>
>>> On Wed, Dec 30, 2015 at 1:34 PM Khem Raj <raj.k...@gmail.com> wrote:
>>>
>>>> On Wed, Dec 30, 2015 at 10:27 AM, Giordon Stark <kra...@gmail.com>
>>>> wrote:
>>>> > I'll look at pkg-config examples. How do I fix the llvm issue though?
>>>> I
>>>> > don't know enough about bitbake to fix that.
>>>>
>>>> disable, internal build _somehow_
>>>> then add DEPENDS += "llvm3" to recipe
>>>> >
>>>> > Giordon
>>>> >
>>>> > On Wed, Dec 30, 2015 at 1:26 PM Khem Raj <raj.k...@gmail.com> wrote:
>>>> >>
>>>> >> you mostly have one of these issues
>>>> >>
>>>> >> | ERROR:
>>>> >> /home/osboxes/poky/build/tmp/sysroots/i686-linux/usr/bin/pcre-config
>>>> >> should not be used, use an alternative such as pkg-config
>>>> >> | ERROR:
>>>> >> /home/osboxes/poky/build/tmp/sysroots/i686-linux/usr/bin/pcre-config
>>>> >> should not be used, use an alternative such as pkg-config
>>>> >> | ERROR:
>>>> >> /home/osboxes/poky/build/tmp/sysroots/i686-linux/usr/bin/pcre-config
>>>> >> should not be used, use an alternative such as pkg-config
>>>> >> | ERROR:
>>>> >> /home/osboxes/poky/build/tmp/sysroots/i686-linux/usr/bin/pcre-config
>>>> >> should not be used, use an alternative such as pkg-config
>>>> >>
>>>> >> so you need to replace the use of pcre-config with pkg-config, there
>>>> >> are example how it has been done for some other recipes in OE
>>>> >>
>>>> >> second problem seems to be that its trying to compile its own version
>>>> >> of llvm and thats failing because the native compiler its finding
>>>> does
>>>> >> not support c++11 or atleast the config tests think that way. Again
>>>> >> this components build system needs to fix that. You might be better
>>>> >> off using llvm provided bt meta-oe instead of internal version.
>>>> >>
>>>> >> On Wed, Dec 30, 2015 at 9:35 AM, Giordon Stark <kra...@gmail.com>
>>>> wrote:
>>>> >> > https://gist.github.com/anonymous/adec2839deecce33702a
>>>> >> >
>>>> >> > Giordon
>>>> >> >
>>>> >> > On Wed, Dec 23, 2015 at 9:25 PM Khem Raj <raj.k...@gmail.com>
>>>> wrote:
>>>> >> >>
>>>> >> >> can you post output of
>>>> root/6.04.12-r0/build/CMakeFiles/CMakeError.log
>>>> >> >>
>>>> >> >> On Wed, Dec 9, 2015 at 12:00 PM, Giordon Stark <kra...@gmail.com>
>>>> >> >> wrote:
>>>> >> >> > Hi all,
>>>> >> >> >
>>>> >> >> > I'm trying to add a recipe for ROOT (from CERN) but I'm running
>>>> into
>>>> >> >> > various
>>>> >> >> > issues with just trying to get compilers working.
>>>> >> >> >
>>>> >> >> > Current recipe:
>>>> >> >> >
>>>> >> >> >
>>>> >> >> >
>>>> https://github.com/kratsg/meta-l1calo/blob/master/recipes-core/root/root_6.04.12.bb
>>>> >> >> >
>>>> >> >> > Current log:
>>>> https://gist.github.com/kratsg/cd3184a167676eb69067
>>>> >> >> >
>>>> >> >> > Note that the goal is to have the bare-minimum with PyROOT
>>>> (enable
>>>> >> >> > python
>>>> >> >> > support). So I'm following:
>>>> >> >> > - https://root.cern.ch/building-root
>>>> >> >> > - https://root.cern.ch/build-prerequisites
>>>> >> >> >
>>>> >> >> > Thanks,
>>>> >> >> >
>>>> >> >> > Giordon
>>>> >> >> >
>>>> >> >> > --
>>>> >> >> > ___
>>>> >> >> > yocto mailing list
>>>> >> >> > yocto@yoctoproject.org
>>>> >> >> > https://lists.yoctoproject.org/listinfo/yocto
>>>> >> >> >
>>>>
>>>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Trying to add a recipe for ROOT

[Giordon Stark]

I'll look at pkg-config examples. How do I fix the llvm issue though? I
don't know enough about bitbake to fix that.

Giordon

On Wed, Dec 30, 2015 at 1:26 PM Khem Raj <raj.k...@gmail.com> wrote:

> you mostly have one of these issues
>
> | ERROR:
> /home/osboxes/poky/build/tmp/sysroots/i686-linux/usr/bin/pcre-config
> should not be used, use an alternative such as pkg-config
> | ERROR:
> /home/osboxes/poky/build/tmp/sysroots/i686-linux/usr/bin/pcre-config
> should not be used, use an alternative such as pkg-config
> | ERROR:
> /home/osboxes/poky/build/tmp/sysroots/i686-linux/usr/bin/pcre-config
> should not be used, use an alternative such as pkg-config
> | ERROR:
> /home/osboxes/poky/build/tmp/sysroots/i686-linux/usr/bin/pcre-config
> should not be used, use an alternative such as pkg-config
>
> so you need to replace the use of pcre-config with pkg-config, there
> are example how it has been done for some other recipes in OE
>
> second problem seems to be that its trying to compile its own version
> of llvm and thats failing because the native compiler its finding does
> not support c++11 or atleast the config tests think that way. Again
> this components build system needs to fix that. You might be better
> off using llvm provided bt meta-oe instead of internal version.
>
> On Wed, Dec 30, 2015 at 9:35 AM, Giordon Stark <kra...@gmail.com> wrote:
> > https://gist.github.com/anonymous/adec2839deecce33702a
> >
> > Giordon
> >
> > On Wed, Dec 23, 2015 at 9:25 PM Khem Raj <raj.k...@gmail.com> wrote:
> >>
> >> can you post output of root/6.04.12-r0/build/CMakeFiles/CMakeError.log
> >>
> >> On Wed, Dec 9, 2015 at 12:00 PM, Giordon Stark <kra...@gmail.com>
> wrote:
> >> > Hi all,
> >> >
> >> > I'm trying to add a recipe for ROOT (from CERN) but I'm running into
> >> > various
> >> > issues with just trying to get compilers working.
> >> >
> >> > Current recipe:
> >> >
> >> >
> https://github.com/kratsg/meta-l1calo/blob/master/recipes-core/root/root_6.04.12.bb
> >> >
> >> > Current log: https://gist.github.com/kratsg/cd3184a167676eb69067
> >> >
> >> > Note that the goal is to have the bare-minimum with PyROOT (enable
> >> > python
> >> > support). So I'm following:
> >> > - https://root.cern.ch/building-root
> >> > - https://root.cern.ch/build-prerequisites
> >> >
> >> > Thanks,
> >> >
> >> > Giordon
> >> >
> >> > --
> >> > ___
> >> > yocto mailing list
> >> > yocto@yoctoproject.org
> >> > https://lists.yoctoproject.org/listinfo/yocto
> >> >
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Trying to add a recipe for ROOT

[Giordon Stark]

https://gist.github.com/anonymous/adec2839deecce33702a

Giordon

On Wed, Dec 23, 2015 at 9:25 PM Khem Raj <raj.k...@gmail.com> wrote:

> can you post output of root/6.04.12-r0/build/CMakeFiles/CMakeError.log
>
> On Wed, Dec 9, 2015 at 12:00 PM, Giordon Stark <kra...@gmail.com> wrote:
> > Hi all,
> >
> > I'm trying to add a recipe for ROOT (from CERN) but I'm running into
> various
> > issues with just trying to get compilers working.
> >
> > Current recipe:
> >
> https://github.com/kratsg/meta-l1calo/blob/master/recipes-core/root/root_6.04.12.bb
> >
> > Current log: https://gist.github.com/kratsg/cd3184a167676eb69067
> >
> > Note that the goal is to have the bare-minimum with PyROOT (enable python
> > support). So I'm following:
> > - https://root.cern.ch/building-root
> > - https://root.cern.ch/build-prerequisites
> >
> > Thanks,
> >
> > Giordon
> >
> > --
> > ___
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
> >
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Trying to add a recipe for ROOT

[Giordon Stark]

I'm unable to disable the internal build. I'm working on the pkg-config
however.

On Wed, Dec 30, 2015 at 1:34 PM Khem Raj <raj.k...@gmail.com> wrote:

> On Wed, Dec 30, 2015 at 10:27 AM, Giordon Stark <kra...@gmail.com> wrote:
> > I'll look at pkg-config examples. How do I fix the llvm issue though? I
> > don't know enough about bitbake to fix that.
>
> disable, internal build _somehow_
> then add DEPENDS += "llvm3" to recipe
> >
> > Giordon
> >
> > On Wed, Dec 30, 2015 at 1:26 PM Khem Raj <raj.k...@gmail.com> wrote:
> >>
> >> you mostly have one of these issues
> >>
> >> | ERROR:
> >> /home/osboxes/poky/build/tmp/sysroots/i686-linux/usr/bin/pcre-config
> >> should not be used, use an alternative such as pkg-config
> >> | ERROR:
> >> /home/osboxes/poky/build/tmp/sysroots/i686-linux/usr/bin/pcre-config
> >> should not be used, use an alternative such as pkg-config
> >> | ERROR:
> >> /home/osboxes/poky/build/tmp/sysroots/i686-linux/usr/bin/pcre-config
> >> should not be used, use an alternative such as pkg-config
> >> | ERROR:
> >> /home/osboxes/poky/build/tmp/sysroots/i686-linux/usr/bin/pcre-config
> >> should not be used, use an alternative such as pkg-config
> >>
> >> so you need to replace the use of pcre-config with pkg-config, there
> >> are example how it has been done for some other recipes in OE
> >>
> >> second problem seems to be that its trying to compile its own version
> >> of llvm and thats failing because the native compiler its finding does
> >> not support c++11 or atleast the config tests think that way. Again
> >> this components build system needs to fix that. You might be better
> >> off using llvm provided bt meta-oe instead of internal version.
> >>
> >> On Wed, Dec 30, 2015 at 9:35 AM, Giordon Stark <kra...@gmail.com>
> wrote:
> >> > https://gist.github.com/anonymous/adec2839deecce33702a
> >> >
> >> > Giordon
> >> >
> >> > On Wed, Dec 23, 2015 at 9:25 PM Khem Raj <raj.k...@gmail.com> wrote:
> >> >>
> >> >> can you post output of
> root/6.04.12-r0/build/CMakeFiles/CMakeError.log
> >> >>
> >> >> On Wed, Dec 9, 2015 at 12:00 PM, Giordon Stark <kra...@gmail.com>
> >> >> wrote:
> >> >> > Hi all,
> >> >> >
> >> >> > I'm trying to add a recipe for ROOT (from CERN) but I'm running
> into
> >> >> > various
> >> >> > issues with just trying to get compilers working.
> >> >> >
> >> >> > Current recipe:
> >> >> >
> >> >> >
> >> >> >
> https://github.com/kratsg/meta-l1calo/blob/master/recipes-core/root/root_6.04.12.bb
> >> >> >
> >> >> > Current log: https://gist.github.com/kratsg/cd3184a167676eb69067
> >> >> >
> >> >> > Note that the goal is to have the bare-minimum with PyROOT (enable
> >> >> > python
> >> >> > support). So I'm following:
> >> >> > - https://root.cern.ch/building-root
> >> >> > - https://root.cern.ch/build-prerequisites
> >> >> >
> >> >> > Thanks,
> >> >> >
> >> >> > Giordon
> >> >> >
> >> >> > --
> >> >> > ___
> >> >> > yocto mailing list
> >> >> > yocto@yoctoproject.org
> >> >> > https://lists.yoctoproject.org/listinfo/yocto
> >> >> >
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Trying to add a recipe for ROOT

[Giordon Stark]

Here's an update set of logs:

(output) https://gist.github.com/anonymous/56f904b65feeb3346db6
(CMakeError.log) https://gist.github.com/anonymous/d5d766badcee1df5efc1

for the current recipe here:
https://github.com/kratsg/meta-l1calo/blob/master/recipes-core/root/root_6.04.12.bb

On Wed, Dec 30, 2015 at 2:10 PM Giordon Stark <kra...@gmail.com> wrote:

> Actually -- if you look here -- I'm already using pkg-config?
>
>
> https://github.com/kratsg/meta-l1calo/blob/master/recipes-core/root/root_6.04.12.bb#L9
>
> Is there something wrong with the configuration then?
>
> On Wed, Dec 30, 2015 at 2:07 PM Giordon Stark <kra...@gmail.com> wrote:
>
>> I'm unable to disable the internal build. I'm working on the pkg-config
>> however.
>>
>> On Wed, Dec 30, 2015 at 1:34 PM Khem Raj <raj.k...@gmail.com> wrote:
>>
>>> On Wed, Dec 30, 2015 at 10:27 AM, Giordon Stark <kra...@gmail.com>
>>> wrote:
>>> > I'll look at pkg-config examples. How do I fix the llvm issue though? I
>>> > don't know enough about bitbake to fix that.
>>>
>>> disable, internal build _somehow_
>>> then add DEPENDS += "llvm3" to recipe
>>> >
>>> > Giordon
>>> >
>>> > On Wed, Dec 30, 2015 at 1:26 PM Khem Raj <raj.k...@gmail.com> wrote:
>>> >>
>>> >> you mostly have one of these issues
>>> >>
>>> >> | ERROR:
>>> >> /home/osboxes/poky/build/tmp/sysroots/i686-linux/usr/bin/pcre-config
>>> >> should not be used, use an alternative such as pkg-config
>>> >> | ERROR:
>>> >> /home/osboxes/poky/build/tmp/sysroots/i686-linux/usr/bin/pcre-config
>>> >> should not be used, use an alternative such as pkg-config
>>> >> | ERROR:
>>> >> /home/osboxes/poky/build/tmp/sysroots/i686-linux/usr/bin/pcre-config
>>> >> should not be used, use an alternative such as pkg-config
>>> >> | ERROR:
>>> >> /home/osboxes/poky/build/tmp/sysroots/i686-linux/usr/bin/pcre-config
>>> >> should not be used, use an alternative such as pkg-config
>>> >>
>>> >> so you need to replace the use of pcre-config with pkg-config, there
>>> >> are example how it has been done for some other recipes in OE
>>> >>
>>> >> second problem seems to be that its trying to compile its own version
>>> >> of llvm and thats failing because the native compiler its finding does
>>> >> not support c++11 or atleast the config tests think that way. Again
>>> >> this components build system needs to fix that. You might be better
>>> >> off using llvm provided bt meta-oe instead of internal version.
>>> >>
>>> >> On Wed, Dec 30, 2015 at 9:35 AM, Giordon Stark <kra...@gmail.com>
>>> wrote:
>>> >> > https://gist.github.com/anonymous/adec2839deecce33702a
>>> >> >
>>> >> > Giordon
>>> >> >
>>> >> > On Wed, Dec 23, 2015 at 9:25 PM Khem Raj <raj.k...@gmail.com>
>>> wrote:
>>> >> >>
>>> >> >> can you post output of
>>> root/6.04.12-r0/build/CMakeFiles/CMakeError.log
>>> >> >>
>>> >> >> On Wed, Dec 9, 2015 at 12:00 PM, Giordon Stark <kra...@gmail.com>
>>> >> >> wrote:
>>> >> >> > Hi all,
>>> >> >> >
>>> >> >> > I'm trying to add a recipe for ROOT (from CERN) but I'm running
>>> into
>>> >> >> > various
>>> >> >> > issues with just trying to get compilers working.
>>> >> >> >
>>> >> >> > Current recipe:
>>> >> >> >
>>> >> >> >
>>> >> >> >
>>> https://github.com/kratsg/meta-l1calo/blob/master/recipes-core/root/root_6.04.12.bb
>>> >> >> >
>>> >> >> > Current log: https://gist.github.com/kratsg/cd3184a167676eb69067
>>> >> >> >
>>> >> >> > Note that the goal is to have the bare-minimum with PyROOT
>>> (enable
>>> >> >> > python
>>> >> >> > support). So I'm following:
>>> >> >> > - https://root.cern.ch/building-root
>>> >> >> > - https://root.cern.ch/build-prerequisites
>>> >> >> >
>>> >> >> > Thanks,
>>> >> >> >
>>> >> >> > Giordon
>>> >> >> >
>>> >> >> > --
>>> >> >> > ___
>>> >> >> > yocto mailing list
>>> >> >> > yocto@yoctoproject.org
>>> >> >> > https://lists.yoctoproject.org/listinfo/yocto
>>> >> >> >
>>>
>>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Trying to add a recipe for ROOT

[Giordon Stark]

Actually -- if you look here -- I'm already using pkg-config?

https://github.com/kratsg/meta-l1calo/blob/master/recipes-core/root/root_6.04.12.bb#L9

Is there something wrong with the configuration then?

On Wed, Dec 30, 2015 at 2:07 PM Giordon Stark <kra...@gmail.com> wrote:

> I'm unable to disable the internal build. I'm working on the pkg-config
> however.
>
> On Wed, Dec 30, 2015 at 1:34 PM Khem Raj <raj.k...@gmail.com> wrote:
>
>> On Wed, Dec 30, 2015 at 10:27 AM, Giordon Stark <kra...@gmail.com> wrote:
>> > I'll look at pkg-config examples. How do I fix the llvm issue though? I
>> > don't know enough about bitbake to fix that.
>>
>> disable, internal build _somehow_
>> then add DEPENDS += "llvm3" to recipe
>> >
>> > Giordon
>> >
>> > On Wed, Dec 30, 2015 at 1:26 PM Khem Raj <raj.k...@gmail.com> wrote:
>> >>
>> >> you mostly have one of these issues
>> >>
>> >> | ERROR:
>> >> /home/osboxes/poky/build/tmp/sysroots/i686-linux/usr/bin/pcre-config
>> >> should not be used, use an alternative such as pkg-config
>> >> | ERROR:
>> >> /home/osboxes/poky/build/tmp/sysroots/i686-linux/usr/bin/pcre-config
>> >> should not be used, use an alternative such as pkg-config
>> >> | ERROR:
>> >> /home/osboxes/poky/build/tmp/sysroots/i686-linux/usr/bin/pcre-config
>> >> should not be used, use an alternative such as pkg-config
>> >> | ERROR:
>> >> /home/osboxes/poky/build/tmp/sysroots/i686-linux/usr/bin/pcre-config
>> >> should not be used, use an alternative such as pkg-config
>> >>
>> >> so you need to replace the use of pcre-config with pkg-config, there
>> >> are example how it has been done for some other recipes in OE
>> >>
>> >> second problem seems to be that its trying to compile its own version
>> >> of llvm and thats failing because the native compiler its finding does
>> >> not support c++11 or atleast the config tests think that way. Again
>> >> this components build system needs to fix that. You might be better
>> >> off using llvm provided bt meta-oe instead of internal version.
>> >>
>> >> On Wed, Dec 30, 2015 at 9:35 AM, Giordon Stark <kra...@gmail.com>
>> wrote:
>> >> > https://gist.github.com/anonymous/adec2839deecce33702a
>> >> >
>> >> > Giordon
>> >> >
>> >> > On Wed, Dec 23, 2015 at 9:25 PM Khem Raj <raj.k...@gmail.com> wrote:
>> >> >>
>> >> >> can you post output of
>> root/6.04.12-r0/build/CMakeFiles/CMakeError.log
>> >> >>
>> >> >> On Wed, Dec 9, 2015 at 12:00 PM, Giordon Stark <kra...@gmail.com>
>> >> >> wrote:
>> >> >> > Hi all,
>> >> >> >
>> >> >> > I'm trying to add a recipe for ROOT (from CERN) but I'm running
>> into
>> >> >> > various
>> >> >> > issues with just trying to get compilers working.
>> >> >> >
>> >> >> > Current recipe:
>> >> >> >
>> >> >> >
>> >> >> >
>> https://github.com/kratsg/meta-l1calo/blob/master/recipes-core/root/root_6.04.12.bb
>> >> >> >
>> >> >> > Current log: https://gist.github.com/kratsg/cd3184a167676eb69067
>> >> >> >
>> >> >> > Note that the goal is to have the bare-minimum with PyROOT (enable
>> >> >> > python
>> >> >> > support). So I'm following:
>> >> >> > - https://root.cern.ch/building-root
>> >> >> > - https://root.cern.ch/build-prerequisites
>> >> >> >
>> >> >> > Thanks,
>> >> >> >
>> >> >> > Giordon
>> >> >> >
>> >> >> > --
>> >> >> > ___
>> >> >> > yocto mailing list
>> >> >> > yocto@yoctoproject.org
>> >> >> > https://lists.yoctoproject.org/listinfo/yocto
>> >> >> >
>>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Trying to add a recipe for ROOT

[Giordon Stark]

Hi,

I've not heard a response yet on this?

Giordon

On Wed, Dec 9, 2015 at 3:00 PM Giordon Stark <kra...@gmail.com> wrote:

> Hi all,
>
> I'm trying to add a recipe for ROOT (from CERN) but I'm running into
> various issues with just trying to get compilers working.
>
> Current recipe:
> https://github.com/kratsg/meta-l1calo/blob/master/recipes-core/root/root_6.04.12.bb
>
> Current log: https://gist.github.com/kratsg/cd3184a167676eb69067
>
> Note that the goal is to have the bare-minimum with PyROOT (enable python
> support). So I'm following:
> - https://root.cern.ch/building-root
> - https://root.cern.ch/build-prerequisites
>
> Thanks,
>
> Giordon
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Trying to add a recipe for ROOT

[Giordon Stark]

Hi all,

I'm trying to add a recipe for ROOT (from CERN) but I'm running into
various issues with just trying to get compilers working.

Current recipe:
https://github.com/kratsg/meta-l1calo/blob/master/recipes-core/root/root_6.04.12.bb

Current log: https://gist.github.com/kratsg/cd3184a167676eb69067

Note that the goal is to have the bare-minimum with PyROOT (enable python
support). So I'm following:
- https://root.cern.ch/building-root
- https://root.cern.ch/build-prerequisites

Thanks,

Giordon
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto