Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Romain Naour <romain.naour@smile.fr>
Cc: David GOUARIN <dgouarin@gmail.com>,
	David GOUARIN <david.gouarin@thalesgroup.com>,
	Matt Weber <matthew.weber@collins.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2/2] package/libtalloc: bump version to 2.3.4
Date: Sun, 24 Jul 2022 12:54:13 +0200	[thread overview]
Message-ID: <20220724105413.GT2641@scaer> (raw)
In-Reply-To: <30f9fc02-781b-27ac-ecec-5f03680f8a7d@smile.fr>

Romain, All,

On 2022-07-24 10:55 +0200, Romain Naour spake thusly:
> Le 24/07/2022 à 10:46, Yann E. MORIN a écrit :
> > On 2022-07-24 10:19 +0200, Romain Naour spake thusly:
[--SNIP--]
> >> I found another commit adding the offending waf check:
> >> https://gitlab.com/samba-team/samba/-/commit/420bbb1d92fd2a28725b53f425ba3d214831b660
> >> because it doesn't work without PYTHONHASHSEED.
> > I am not sure "it doesn't work without PYTHONHASHSEED".
> I mean, I tried locally because I wanted to know :)
> The build stop with this error message:
> "PYTHONHASHSEED=1 missing! Don't use waf directly, use ./configure and make!"

OK, I was looking at the git repository for talloc, and it does not have
that test at all. It never had. Only the release tarball has. Weird...
:-(

Meh. Must be exoplained in the commit log...

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

  reply	other threads:[~2022-07-24 10:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-05 13:44 [Buildroot] [PATCH 1/2] package/pkg-waf.mk: enable definiton of env. variables in every build steps David GOUARIN
2022-07-05 13:44 ` [Buildroot] [PATCH 2/2] package/libtalloc: bump version to 2.3.4 David GOUARIN
2022-07-23 17:15   ` Romain Naour
2022-07-24  7:59     ` Yann E. MORIN
2022-07-24  8:19       ` Romain Naour
2022-07-24  8:46         ` Yann E. MORIN
2022-07-24  8:55           ` Romain Naour
2022-07-24 10:54             ` Yann E. MORIN [this message]
2022-07-23 22:26 ` [Buildroot] [PATCH 1/2] package/pkg-waf.mk: enable definiton of env. variables in every build steps Yann E. MORIN
2022-08-16 19:59 ` Peter Korsgaard

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=20220724105413.GT2641@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@buildroot.org \
    --cc=david.gouarin@thalesgroup.com \
    --cc=dgouarin@gmail.com \
    --cc=matthew.weber@collins.com \
    --cc=romain.naour@smile.fr \
    /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