From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Sourabh Hegde <hrsourabh011@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] Missing curl binary
Date: Sat, 18 Feb 2023 12:18:46 +0100 [thread overview]
Message-ID: <20230218121846.306f95f5@windsurf> (raw)
In-Reply-To: <CADYjeStw7HOAxA_ipNUNW4EsQzUZQydhW+Uaa8_UusE_wisy-g@mail.gmail.com>
On Fri, 17 Feb 2023 16:52:49 +0100
Sourabh Hegde <hrsourabh011@gmail.com> wrote:
> I am trying to include curl binary in my image. I have
> selected BR2_PACKAGE_LIBCURL=y , BR2_PACKAGE_LIBCURL_CURL=y in the Config.
> But still the curl binary is not installed in the target. Can anyone please
> let me know what is the issue here and how to resolve it?
I suppose you did a build with BR2_PACKAGE_LIBCURL=y, then after the
build completed you changed the configuration to enable
BR2_PACKAGE_LIBCURL_CURL=y and just ran "make". This doesn't work, as
the libcurl package is already built, and Buildroot is not smart enough
to detect that you changed something related to the libcurl
configuration.
Run: "make libcurl-dirclean all" to force rebuilding the libcurl
package (or do a full rebuild).
See https://buildroot.org/downloads/manual/manual.html#full-rebuild for
more details.
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-02-18 11:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 15:52 [Buildroot] Missing curl binary Sourabh Hegde
2023-02-18 10:28 ` Sourabh Hegde
2023-02-18 11:18 ` Thomas Petazzoni via buildroot [this message]
2023-02-18 17:09 ` Sourabh Hegde
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=20230218121846.306f95f5@windsurf \
--to=buildroot@buildroot.org \
--cc=hrsourabh011@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
/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