From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Adam Duskett <aduskett@gmail.com>
Cc: Joseph Kogut <joseph.kogut@gmail.com>,
Buildroot List <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH] package/sentry-cli: remove package
Date: Thu, 19 Aug 2021 18:19:26 +0200 [thread overview]
Message-ID: <20210819181926.771fe4f1@windsurf> (raw)
In-Reply-To: <CAFSsvmqmKHD0k4fOWAV+Zdj+m=jSvafFYtw1vMsOj1Jf5rRMSA@mail.gmail.com>
On Thu, 19 Aug 2021 09:08:49 -0700
Adam Duskett <aduskett@gmail.com> wrote:
> Interestingly enough, my testing method was flawed. While I did spin
> up a debian 9
> docker container and the exact git hash that failed, I made the
> mistake of running
> `make host-sentry-cli` and not `make`
>
> When calling host-sentry-cli directly, there isn't a failure, but when
> running just `make`
> the failure does appear. I am not sure how to pass include paths to
> cargo, but it seems
> like the only failure now is the missing zlib.h library if the package
> is bumped to 1.68, as
> the git repository error is indeed resolved.
Including for an out-of-tree build, where the build directory is
outside of any Git repository ?
Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-08-19 16:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-18 20:22 [Buildroot] [PATCH] package/sentry-cli: remove package Thomas Petazzoni
2021-08-18 20:36 ` Adam Duskett
2021-08-18 21:54 ` Thomas Petazzoni
2021-08-19 16:08 ` Adam Duskett
2021-08-19 16:19 ` Thomas Petazzoni [this message]
2021-08-19 16:30 ` Adam Duskett
2021-08-19 17:56 ` Thomas Petazzoni
2021-08-19 20:50 ` Yann E. MORIN
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=20210819181926.771fe4f1@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=aduskett@gmail.com \
--cc=buildroot@buildroot.org \
--cc=joseph.kogut@gmail.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