Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error on make menuconfig: ~/Projects/local_buildroot/Config.in:1: can't open file "/Projects/local_buildroot/package/Config.in" #1

Open
lennybacon opened this issue Dec 20, 2024 · 0 comments

Comments

@lennybacon
Copy link

I followed the description and executed the following commands

mkdir -p ~/Projects/local_buildroot
cd ~/Projects
git clone git://git.buildroot.net/buildroot
cd local_buildroot
git init
mkdir configs package

echo 'name: LOCAL_BUILDROOT' > external.desc
echo 'include $(sort $(wildcard $(BR2_EXTERNAL_LOCAL_BUILDROOT_PATH)/package/*/*.mk))' > external.mk
echo 'source "$BR2_EXTERNAL_LOCAL_BUILDROOT_PATH/package/Config.in"' > Config.in

Inside my ~/Projects/local_buildroot directory I now have two empty directories (configs and package) and the three config files (external.desc, external.mk and Config.in). There are no files in the package directory.

Now I continue to run the commands documented.

git add *
git commit

cd ~/Projects/buildroot
export BR2_EXTERNAL=${HOME}/Projects/local_buildroot
make menuconfig

The output of the command make menuconfig gives me an error, complaining about a file it cannot open:

/home/df/Projects/local_buildroot/Config.in:1: can't open file "/home/df/Projects/local_buildroot/package/Config.in"
make[1]: *** [Makefile:992: menuconfig] Error 1
make: *** [Makefile:83: _all] Error 2

I definitively have not created the file inside the packages directory. The Config.in in the local_buildroot points to a file with the same name but underneath the package directory, which I created and is empty.

So where is the file ~/Projects/local_buildroot/package/Config.in supposed to come from? Am I missing something or is ther some step in the config missing?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant