Re: [yocto] Building gdb-7.10 for arm with master
On 5 March 2016 at 21:19, Rudolf J Streif wrote: > compile fails with the following error message: > > | make[2]: *** No rule to make target '../readline/libreadline.a', needed > by 'gdb'. Stop. > | make[2]: *** Waiting for unfinished jobs > > The reason seems to be a broken path to the built-in readline in the > makefile as the default configuration is > --without-system-readline. Enabling > > PACKAGECONFIG_append_pn-dbg = " readline" > The default is with system readline... gdb-common.inc:PACKAGECONFIG ??= "readline" However if you do have PACKAGECONFIG set to "" for gdb for some reason then you'll want to cherry-pick ce2542057d877044a7548f2884d192f4f672c75a (master-next) to fix builds with the internal readline if you've got no-static-libs enabled (which is true for Poky). Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Building gdb-7.10 for arm with master
At least for arm (I have not tested other arch) building gdb-7.10 with Build Configuration: BB_VERSION= "1.29.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "Fedora-22" TARGET_SYS= "arm-poky-linux-gnueabi" MACHINE = "beaglebone" DISTRO= "poky" DISTRO_VERSION= "2.0+snapshot-20160305" TUNE_FEATURES = "arm armv7a vfp neoncallconvention-hard cortexa8" TARGET_FPU= "hard" meta meta-poky meta-yocto-bsp= "master:5cd71fe432c9bdfd3ff519543e96e8caa2b7cf6c" meta-oe meta-python = "master:36aab3f797630e3de680a88523f40ead4ca95d28" meta-qt5 = "master:88a7f264ef5f64d73881c384d22bf883b2cbf72e" compile fails with the following error message: | make[2]: *** No rule to make target '../readline/libreadline.a', needed by 'gdb'. Stop. | make[2]: *** Waiting for unfinished jobs The reason seems to be a broken path to the built-in readline in the makefile as the default configuration is --without-system-readline. Enabling PACKAGECONFIG_append_pn-dbg = " readline" solves the problem. I wonder if anybody else has observed this problem? Cheers, Rudi -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Howto change the default shell in yocto?
On 5 March 2016 at 11:48, Oliver Graute wrote: > first the default *system* shell (/bin/sh) is this possible? or does this > affect > to much of the yoco system itself, if I change /bin/sh to /bin/dash? > bash is only the default shell (ie symlink from /bin/sh) if you install it, so if you don't want bash to be sh then one option is to not install bash. If you do want to keep bash installed but change the sh link, then that is managed with update-alternatives. Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Question - getting started with HIO-EMB-1200 core-board
I have bought an HIO-EMB-1200 core-board with an HIO-IOB-1240 IO module. I would like to compile, build and deploy executables to the board from an IDE on my Windows 8.1 machine. What is the best IDE for debugging the code while it's running on the board? I intend to develop a SIP user agent and run it on the board. The SIP UA will auto-answer inbound calls and can place outbound calls to a pre-configured number. Outbound calls will be placed on detection of a signal (user pressing a HW button). I am wondering if the default image/os/kernel on the board should be switched out with another image/os/kernel (not sure which word to use here) ? I have been told that it's possible to run the Android OS on this board? If that's true, how do I make the board run Android? I believe that I would have to write an Android OS image to an SDCARD and let the board boot from the SDCARD? Is it possible to "flash" the board so that it boots Android from a persistent storage (not SDCARD) ? Thanks -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Howto change the default shell in yocto?
On 04/03/16, Christopher Larson wrote: > The default *system* shell (/bin/sh) or the default shell for users, or for > root? Folks often conflate them, but they're not the same. first the default *system* shell (/bin/sh) is this possible? or does this affect to much of the yoco system itself, if I change /bin/sh to /bin/dash? the alternative for me is to just change the default shell for normal users and the root user. I assume its done via /etc/passwd. But how I adapt these the yocto way? Best regards, Oliver -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
