From: "Mark Hatle" <mark.hatle@kernel.crashing.org>
To: R Keith Beal <r@cmss.com>, yocto@lists.yoctoproject.org
Subject: Re: [yocto] Yocto gdb build error on Microblaze platform
Date: Fri, 5 Jun 2020 15:23:36 -0500 [thread overview]
Message-ID: <e5dc4586-d1a8-69e9-c3c5-9657637ccbc3@kernel.crashing.org> (raw)
In-Reply-To: <95d62cb9-5791-970e-4397-488c497afa61@CMSS.com>
This could be an issue with your host if the host is too old. Unfortunately
I've not worked with the releases that are that old.
However, Xilinx did just release their 'Zeus' based rel-v2020.1 version. That
version should work on most modern hosts (ones that Zeus works against.) Even
if you are debugging older code the newer debugger should work, so it might be
an option for you.
--Mark
On 6/5/20 3:02 PM, R Keith Beal wrote:
> Fellow Developers,
>
>
> I am attempting to add gdb to a Yocto project based on Yocto 2.3 (Pyro).
>
> The build complains about a missing libreadline.a.
>
>
> *| make[2]: Leaving directory
> '/opt/yocto/yocto-bwc/builds/microblazeel/tmp/work/microblazeel-v9.6-bs-cmp-mh-poky-linux/gdb/7.7.1-r0/build-microblazeel-poky-linux/opcodes'*
>
> *| make[2]: Entering directory
> '/opt/yocto/yocto-bwc/builds/microblazeel/tmp/work/microblazeel-v9.6-bs-cmp-mh-poky-linux/gdb/7.7.1-r0/build-microblazeel-poky-linux/gdb'*
>
> *| make[2]: *** No rule to make target '../readline/libreadline.a', needed by
> 'gdb'. Stop.*
>
> *| make[2]: *** Waiting for unfinished jobs....*
>
>
>
> I tried several solutions from related searches.
>
> https://www.yoctoproject.org/pipermail/yocto/2017-June/036676.html
> <http://url1567.cmss.com/ls/click?upn=THw5ysdXae-2B-2Btp69CrkSktfnnmsBMoq2fcLowO1MzKn3wcqowiND-2FTX2Ck09GJGF11Hdqxt9-2BJySKGonPkx0-2FvLNAXTq0WYwTE0-2B6Uyz0Q0-3Ds3H8_onOgH4hKli5v9BePnk5WifnzSD-2FkMXWD4UBJN0NMhyEtRPVSpGiaaE75TdAV5HSL3C5-2Fi5n-2BDKHGDeEkTPVb-2Fb7gapUyik7iAzbey0Nv6Nh1PPsPq0e6zs-2FHGTQciMLMokCWW2i0XDtIP1PxZS-2FBaX9nG8vzU0xSEsOh5-2B-2BNrbSSvAUSyjTopTajwQc0OlCGBRmdkOAlI4rLI2-2FbXadatAeHM2ppplObheY876Um-2F7s-3D>
>
> https://yocto.yoctoproject.narkive.com/gUVw5u2k/failed-to-build-gdb
> <http://url1567.cmss.com/ls/click?upn=THw5ysdXae-2B-2Btp69CrkSkhlnHi-2FYRYLnr3RlrnNZXmyK27CyplgiatU0F3nje-2FAXjDAERK7GpIYABqm2VrjansniTichrksQOsPzjrfGRnQ-3D3jnn_onOgH4hKli5v9BePnk5WifnzSD-2FkMXWD4UBJN0NMhyEtRPVSpGiaaE75TdAV5HSL3C5-2Fi5n-2BDKHGDeEkTPVb-2FROKHNngrTHmIDyLyzUDU4zrfMIpo78C2wBlDsxv8-2BZrviAWCn1byCAfT7YiEftQVK3DN3LssMFNwtjmKXL-2FfZ3nlLFAqjcUW5B7S21IzlkqE9-2BhkLOYjNKhAmXnXDCrWhn8go40EayViSLFCcW2bIE-3D>
>
>
>
> Tried *PACKAGECONFIG_remove_pn-gdb = "readline"* but it does not help.
>
> Tried adding *EXTRA_OECONF_append = " --without-system-readline"* to the image
> recipe but it doesn’t help.**
>
>
>
> From
> /opt/yocto/yocto-bwc/builds/microblazeel/tmp/work/microblazeel-v9.6-bs-cmp-mh-poky-linux/gdb/7.7.1-r0/gdb-7.7.1/gdb/Makefile.in
>
> *# Where is the READLINE library? Typically in ../readline.*
>
> *READLINE_DIR = ../readline*
>
> *READLINE_SRC = $(srcdir)/$(READLINE_DIR)*
>
> *READLINE = @READLINE@*
>
> *READLINE_DEPS = @READLINE_DEPS@*
>
> *READLINE_CFLAGS = @READLINE_CFLAGS@*
>
>
>
> I tried adding *PACKAGECONFIG_remove_pn-gdb = "readline"* to the local.conf**
>
>
> As a test, I manually built gdb’s local copy of readline and I get lots of
> compile errors that look like some sort of version skew with the thread library.
>
> *| In file included from ../../gdb-7.7.1/gdb/proc-service.c:28:0:*
>
> *| ../../gdb-7.7.1/gdb/gdb_proc_service.h:162:9: error: unknown type name
> 'gdb_fpregset_t'*
>
> *| typedef gdb_fpregset_t gdb_prfpregset_t;*
>
> *| ^~~~~~~~~~~~~~*
>
> *| ../../gdb-7.7.1/gdb/proc-service.c:151:1: warning: no previous prototype for
> 'ps_lgetxregsize' [-Wmissing-prototypes]*
>
> *| ps_lgetxregsize (gdb_ps_prochandle_t ph, lwpid_t lwpid, int *xregsize)*
>
> *| ^~~~~~~~~~~~~~~*
>
> *| ../../gdb-7.7.1/gdb/proc-service.c:161:1: warning: no previous prototype for
> 'ps_lgetxregs' [-Wmissing-prototypes]*
>
> *| ps_lgetxregs (gdb_ps_prochandle_t ph, lwpid_t lwpid, caddr_t xregset)*
>
> *| ^~~~~~~~~~~~*
>
> *| ../../gdb-7.7.1/gdb/proc-service.c:171:1: warning: no previous prototype for
> 'ps_lsetxregs' [-Wmissing-prototypes]*
>
> *| ps_lsetxregs (gdb_ps_prochandle_t ph, lwpid_t lwpid, caddr_t xregset)*
>
> *| ^~~~~~~~~~~~*
>
> *| ../../gdb-7.7.1/gdb/proc-service.c:180:1: warning: no previous prototype for
> 'ps_plog' [-Wmissing-prototypes]*
>
> *| ps_plog (const char *fmt, ...)*
>
> *| ^~~~~~~*
>
> *| ../../gdb-7.7.1/gdb/proc-service.c:298:1: error: conflicting types for
> 'ps_lgetfpregs'*
>
> *| ps_lgetfpregs (gdb_ps_prochandle_t ph, lwpid_t lwpid,*
>
> *| ^~~~~~~~~~~~~*
>
> *| In file included from ../../gdb-7.7.1/gdb/gdb_proc_service.h:25:0,*
>
> *| from ../../gdb-7.7.1/gdb/proc-service.c:28:*
>
> *|
> /opt/yocto/yocto-bwc/builds/microblazeel/tmp/work/microblazeel-v9.6-bs-cmp-mh-poky-linux/gdb/7.7.1-r0/recipe-sysroot/usr/include/proc_service.h:61:17:
> note: previous declaration of 'ps_lgetfpregs' was here*
>
> *| extern ps_err_e ps_lgetfpregs (struct ps_prochandle *,*
>
> *| ^~~~~~~~~~~~~*
>
> *| ../../gdb-7.7.1/gdb/proc-service.c:318:1: error: conflicting types for
> 'ps_lsetfpregs'*
>
> *| ps_lsetfpregs (gdb_ps_prochandle_t ph, lwpid_t lwpid,*
>
> *| ^~~~~~~~~~~~~*
>
> *| In file included from ../../gdb-7.7.1/gdb/gdb_proc_service.h:25:0,*
>
> *| from ../../gdb-7.7.1/gdb/proc-service.c:28:*
>
> *|
> /opt/yocto/yocto-bwc/builds/microblazeel/tmp/work/microblazeel-v9.6-bs-cmp-mh-poky-linux/gdb/7.7.1-r0/recipe-sysroot/usr/include/proc_service.h:63:17:
> note: previous declaration of 'ps_lsetfpregs' was here*
>
> *| extern ps_err_e ps_lsetfpregs (struct ps_prochandle *,*
>
> *| ^~~~~~~~~~~~~*
>
> *| ERROR: oe_runmake failed*
>
> *| Makefile:1011: recipe for target 'proc-service.o' failed*
>
> *| make[2]: *** [proc-service.o] Error 1*
>
> *| make[2]: *** Waiting for unfinished jobs....*
>
> *| In file included from ../../gdb-7.7.1/gdb/linux-thread-db.c:24:0:*
>
> *| ../../gdb-7.7.1/gdb/gdb_proc_service.h:162:9: error: unknown type name
> 'gdb_fpregset_t'*
>
> *| typedef gdb_fpregset_t gdb_prfpregset_t;*
>
> *| ^~~~~~~~~~~~~~*
>
> *| Makefile:1011: recipe for target 'linux-thread-db.o' failed*
>
> *| make[2]: *** [linux-thread-db.o] Error 1*
>
> *| make[2]: Leaving directory
> '/opt/yocto/yocto-bwc/builds/microblazeel/tmp/work/microblazeel-v9.6-bs-cmp-mh-poky-linux/gdb/7.7.1-r0/build-microblazeel-poky-linux/gdb'*
>
> *| Makefile:8278: recipe for target 'all-gdb' failed*
>
> *| make[1]: *** [all-gdb] Error 2*
>
> *| make[1]: Leaving directory
> '/opt/yocto/yocto-bwc/builds/microblazeel/tmp/work/microblazeel-v9.6-bs-cmp-mh-poky-linux/gdb/7.7.1-r0/build-microblazeel-poky-linux'*
>
> *| Makefile:832: recipe for target 'all' failed*
>
> *| make: *** [all] Error 2*
>
> *| WARNING:
> /opt/yocto/yocto-bwc/builds/microblazeel/tmp/work/microblazeel-v9.6-bs-cmp-mh-poky-linux/gdb/7.7.1-r0/temp/run.do_compile.18533:1exit
> 1 from 'exit 1'*
>
> *| ERROR: Function failed: do_compile (log file is located at
> /opt/yocto/yocto-bwc/builds/microblazeel/tmp/work/microblazeel-v9.6-bs-cmp-mh-poky-linux/gdb/7.7.1-r0/temp/log.do_compile.18533)*
>
> *ERROR**: Task
> (/opt/yocto/poky/meta-xilinx/recipes-microblaze/gdb/gdb_7.7.1.bb:do_compile)
> failed with exit code '1'*
>
>
>
>
>
>
next prev parent reply other threads:[~2020-06-05 20:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-05 20:02 Yocto gdb build error on Microblaze platform R Keith Beal
2020-06-05 20:23 ` Mark Hatle [this message]
2020-06-06 1:28 ` [yocto] " Khem Raj
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e5dc4586-d1a8-69e9-c3c5-9657637ccbc3@kernel.crashing.org \
--to=mark.hatle@kernel.crashing.org \
--cc=r@cmss.com \
--cc=yocto@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox