From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Sourabh Hegde <hrsourabh011@gmail.com>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] Updating trust store using update-ca-certificates
Date: Sun, 19 Feb 2023 14:17:53 +0100 [thread overview]
Message-ID: <20230219131753.GE2718518@scaer> (raw)
In-Reply-To: <CADYjeSvNkOYY=RCeC9Jg2aX610XyzB5YN2aCq1nYo8U-LGAfTA@mail.gmail.com>
Sourabh, All,
On 2023-02-19 13:53 +0100, Sourabh Hegde spake thusly:
> I think the issue is during build, the [1]ca-certificates.mk is not available in the output/build/ca-certificates/ dir. Only
> Makefile and ca-certificates.crt file is present.
> So how can I patch the makefile?
This is a patch agaisnt Buildroot itself. Apply it to Buildroot.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-02-19 13:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 16:15 [Buildroot] Updating trust store using update-ca-certificates Sourabh Hegde
2023-02-18 11:19 ` Thomas Petazzoni via buildroot
2023-02-18 12:54 ` Sourabh Hegde
2023-02-18 13:19 ` Thomas Petazzoni via buildroot
2023-02-18 13:39 ` Sourabh Hegde
2023-02-18 14:21 ` Yann E. MORIN
2023-02-18 15:32 ` Yann E. MORIN
2023-02-18 15:56 ` Sourabh Hegde
2023-02-18 17:00 ` Sourabh Hegde
2023-02-19 12:53 ` Sourabh Hegde
2023-02-19 13:17 ` Yann E. MORIN [this message]
2023-02-20 10:10 ` 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=20230219131753.GE2718518@scaer \
--to=yann.morin.1998@free.fr \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.