Yocto Project Discussions
 help / color / mirror / Atom feed
From: "Khem Raj" <raj.khem@gmail.com>
To: Mark Hatle <mark.hatle@kernel.crashing.org>,
	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 18:28:06 -0700	[thread overview]
Message-ID: <becd5cba-a728-bbad-cd62-d1e818f261b8@gmail.com> (raw)
In-Reply-To: <e5dc4586-d1a8-69e9-c3c5-9657637ccbc3@kernel.crashing.org>



On 6/5/20 1:23 PM, Mark Hatle wrote:
> 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.**
>>
>>   
>>

Remove readline from PACKAGECONFIG and then
Can you try this patch
https://patchwork.openembedded.org/patch/116843/


      reply	other threads:[~2020-06-06  1:28 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 ` [yocto] " Mark Hatle
2020-06-06  1:28   ` Khem Raj [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=becd5cba-a728-bbad-cd62-d1e818f261b8@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=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