All of lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach via buildroot <buildroot@buildroot.org>
To: "Matthew Silva" <dev@matt-silva.com>
Cc: <buildroot@buildroot.org>
Subject: Re: [Buildroot] [Question] Difficulties with Autotools and nilfs-utils package
Date: Sun, 06 Jul 2025 08:04:02 +0300	[thread overview]
Message-ID: <87ms9hrjul.fsf@tarshish> (raw)
In-Reply-To: <DB4NQ16PKVED.2I7DATK1AFI76@matt-silva.com> (Matthew Silva's message of "Sat, 05 Jul 2025 23:37:38 -0400")

Hi Matthew,

On Sat, Jul 05 2025, Matthew Silva wrote:
> I am in the process of attempting to add partclone
> (https://github.com/Thomas-Tsai/partclone) to buildroot; however, I'm
> running into some issues with its dependency on the nilfs-utils package.
>
> I add it as a dependency both in the Config.in and partclone.mk file but
> when the autotools ./configure runs for partclone, it fails with an
> error saying it is unable to find the "nilfs.h" header file.
>
> Looking at the target /usr/include folder, the nilfs.h header is
> installed there. However, it is not present in the sysroot /usr/include
> folder.
>
> Comparing this to the e2fsprogs dependency that partclone also has, the
> required "ext2fs.h" header file gets installed in both the target AND
> the sysroot /usr/include folders.
>
> My understanding is that autotools is failing because it expects the
> nilfs.h file to be in the sysroot. And it needs to be in the sysroot
> because that is where the cross-compiler (x86_64-buildroot-linux-gnu in
> this case) looks for files when building for the target. (Please correct
> me if I am wrong on either of these).
>
> I am unable to figure out why the nilfs-utils package will not install
> its headers into the sysroot folder. I am not sure if it is a buildroot
> setting or an autotools setting that would be the cause of this issue.

Try adding 'NILFS_UTILS_INSTALL_STAGING = YES' to
package/nilfs-utils/nilfs-utils.mk.

baruch

-- 
                                                     ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2025-07-06  5:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-06  3:37 [Buildroot] [Question] Difficulties with Autotools and nilfs-utils package Matthew Silva
2025-07-06  5:04 ` Baruch Siach via buildroot [this message]
2025-07-06 16:35   ` Matthew Silva

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=87ms9hrjul.fsf@tarshish \
    --to=buildroot@buildroot.org \
    --cc=baruch@tkos.co.il \
    --cc=dev@matt-silva.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.