Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Christian Stewart <christian@aperture.us>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	Buildroot Mailing List <buildroot@buildroot.org>
Subject: Re: [Buildroot] build failure on Ubuntu 22.04 LTS: TIME_BITS=64 is allowed only with FILE_OFFSET_BITS=64
Date: Sat, 17 Feb 2024 18:31:18 +0100	[thread overview]
Message-ID: <ZdDtZo9HnTB5TrUZ@landeda> (raw)
In-Reply-To: <ZdCevcKap6z2nmqV@landeda>

Christian, All,

On 2024-02-17 12:55 +0100, Yann E. MORIN spake thusly:
> On 2024-02-17 01:32 -0800, Christian Stewart via buildroot spake thusly:
> > On a fresh Ubuntu 22.04.4 LTS VM:
> That also happens on Fedora 39.
[--SNIP--]
>     /usr/bin/cpp \
>         -I/home/ymorin/dev/buildroot/O/master/per-package/sudo/host/include \
>         -I../../include \
>         -I../.. \
>         ./sys_signame.h \
>     | /usr/bin/sed -e '1,/^int sudo_end_of_headers;/d' -e '/^#/d' > mksigname.h
>     In file included from /usr/include/features.h:394,
>                      from /usr/include/sys/types.h:25,
>                      from ./sys_signame.h:4:
>     /usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64"
>        26 | #   error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64"
>           |     ^~~~~
[--SNIP--]
>     @@ -65,7 +65,7 @@ define SUDO_BUILD_MKSIGNAME_MKSIGLIST_HOST
>      	-C $(@D)/lib/util mksigname mksiglist
>      endef
> 
>     -SUDO_POST_CONFIGURE_HOOKS += SUDO_BUILD_MKSIGNAME_MKSIGLIST_HOST
>     +#SUDO_POST_CONFIGURE_HOOKS += SUDO_BUILD_MKSIGNAME_MKSIGLIST_HOST
> 
>      define SUDO_PERMISSIONS
>      	/usr/bin/sudo f 4755 0 0 - - - - -
> 
>     $ make sudo-build
>     [ succeeds ]
> 
> OK, so is that supperfluous at all nowadays?
> 
> Can you further investigate, enabling PAM et al in turn and see if any
> optional dependency triggers a call to those two utilities? If not, can
> you look sunce when that is no longer needed and why?

I've now sent a patch for that:

https://patchwork.ozlabs.org/project/buildroot/patch/20240217172923.3629905-1-yann.morin.1998@free.fr/

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:[~2024-02-17 17:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-17  9:32 [Buildroot] build failure on Ubuntu 22.04 LTS: TIME_BITS=64 is allowed only with FILE_OFFSET_BITS=64 Christian Stewart via buildroot
2024-02-17 10:28 ` Christian Stewart via buildroot
2024-02-17 11:55 ` Yann E. MORIN
2024-02-17 17:31   ` Yann E. MORIN [this message]
2024-02-17 17:46   ` 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=ZdDtZo9HnTB5TrUZ@landeda \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@buildroot.org \
    --cc=christian@aperture.us \
    --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