From: Amol Practise <amolpractise@gmail.com>
To: yocto@lists.yoctoproject.org, amolpractise@gmail.com
Cc: Khem Raj <raj.khem@gmail.com>
Subject: Re: [yocto] libtool error
Date: Fri, 29 Mar 2024 00:09:36 +0530 [thread overview]
Message-ID: <CAAkkBwOLnD3fGHahkjbV0VU2Y8Xc3eqFNkeRY1XjDvNY7Prmeg@mail.gmail.com> (raw)
In-Reply-To: <17BFED114E897819.27941@lists.yoctoproject.org>
[-- Attachment #1: Type: text/plain, Size: 2469 bytes --]
Hello team,
i fixed it with below steps
to fix libtool or any package error
do cleanstate of that package
bitbake -c do_cleansstate libtool
do cleanstate of parent package
bitbake -c do_cleansstate gcc
do cleanstate of main image and rerun bitbake
bitbake -c do_cleansstate rpi-test-image
hope it helps
On Mon, Mar 25, 2024 at 11:40 AM Amol Practise via lists.yoctoproject.org
<amolpractise=gmail.com@lists.yoctoproject.org> wrote:
>
> Yes this error is reproducible, there is no memory issues, crashes or
> coredump, i am getting libtool not found error see below lines
>
> | /bin/bash: ./libtool: No such file or directory
> | make[2]: *** [Makefile:612: findcomp.lo] Error 127
> | make[2]: Leaving directory
> '/home/amol/git_repos/poky/rpi-build/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/gcc/13.2.0/gcc-13.2.0/build.arm-poky-linux-gnueabi.arm-poky-linux-gnueabi/libcc1'
> | make[1]: Leaving directory
> '/home/amol/git_repos/poky/rpi-build/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/gcc/13.2.0/gcc-13.2.0/build.arm-poky-linux-gnueabi.arm-poky-linux-gnueabi/libcc1'
> | make[1]: *** [Makefile:443: all] Error 2
> | make: *** [Makefile:11455: all-libcc1] Error 2
> | ERROR: oe_runmake failed
> | WARNING: exit code 1 from a shell command.
> ERROR: Task
> (/home/amol/git_repos/poky/meta/recipes-devtools/gcc/gcc_13.2.bb:do_compile)
> failed with exit code '1'
>
> please guide.
>
> thanks
> amol.
>
> On Mon, Mar 25, 2024 at 7:03 AM Khem Raj <raj.khem@gmail.com> wrote:
>
>> is this error reproducible ? Check if its causing some sort of out of
>> memory errors and crashes on your build system. Can you see if there
>> are some coredumps etc ?
>>
>> On Sun, Mar 24, 2024 at 9:04 AM Amol Practise <amolpractise@gmail.com>
>> wrote:
>> >
>> > Hello ,
>> >
>> > I am getting error while building yocto for raspberry pi , please see
>> attached log file for reference.
>> >
>> > Help is appreciated.
>> >
>> > Thank you.
>> > Amol Palshetkar
>> >
>> >
>> >
>> >
>>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#62836):
> https://lists.yoctoproject.org/g/yocto/message/62836
> Mute This Topic: https://lists.yoctoproject.org/mt/105121719/8370142
> Group Owner: yocto+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [
> amolpractise@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>
[-- Attachment #2: Type: text/html, Size: 5619 bytes --]
prev parent reply other threads:[~2024-03-28 18:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-24 16:03 libtool error Amol Practise
2024-03-25 1:33 ` [yocto] " Khem Raj
2024-03-25 6:10 ` Amol Practise
[not found] ` <17BFED114E897819.27941@lists.yoctoproject.org>
2024-03-28 18:39 ` Amol Practise [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=CAAkkBwOLnD3fGHahkjbV0VU2Y8Xc3eqFNkeRY1XjDvNY7Prmeg@mail.gmail.com \
--to=amolpractise@gmail.com \
--cc=raj.khem@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).