[SOLVED] aarch64-linux-gnu/sys/cdefs.h:24:11: fatal error: features.h: No such file or directory
DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
aarch64-linux-gnu/sys/cdefs.h:24:11: fatal error: features.h: No such file or directory
Hi there!
It would be great if you could assist me on this problem. I do not think it is a question about a missing header file, although it seems so, as I generally can build programs (without using the curl library). It could also be something in the CMakeLists.txt.
I did all kinds of sudo upgrades and updates and build-essential etc..
Anyway, I am getting this message when attempting to build a c++ executable on my raspberry pi 400 (OS is Raspberry PI OS 64 BIT Full version from 2023-10-10) for a pico w. The complete message is as follows:
oti@raspberrypi:~/pico/test/build $ cmake --build .
[ 1%] Performing build step for 'PioasmBuild'
[100%] Built target pioasm
[ 1%] No install step for 'PioasmBuild'
[ 1%] Completed 'PioasmBuild'
[ 4%] Built target PioasmBuild
[ 5%] Built target cyw43_driver_picow_cyw43_bus_pio_spi_pio_h
[ 6%] Performing build step for 'ELF2UF2Build'
[100%] Built target elf2uf2
[ 6%] No install step for 'ELF2UF2Build'
[ 6%] Completed 'ELF2UF2Build'
[ 9%] Built target ELF2UF2Build
[ 10%] Built target bs2_default
[ 11%] Built target bs2_default_padded_checksummed_asm
[ 11%] Building CXX object CMakeFiles/test.dir/test.cpp.obj
In file included from /usr/include/newlib/wchar.h:16,
from /usr/include/newlib/c++/12.2.1/cwchar:44,
from /usr/include/newlib/c++/12.2.1/bits/postypes.h:40,
from /usr/include/newlib/c++/12.2.1/iosfwd:40,
from /usr/include/newlib/c++/12.2.1/ios:38,
from /usr/include/newlib/c++/12.2.1/ostream:38,
from /usr/include/newlib/c++/12.2.1/iostream:39,
from /home/oti/pico/test/test.cpp:1:
/usr/include/aarch64-linux-gnu/sys/cdefs.h:24:11: fatal error: features.h: No such file or directory
24 | # include <features.h>
| ^~~~~~~~~~~~
compilation terminated.
gmake[2]: *** [CMakeFiles/test.dir/build.make:76: CMakeFiles/test.dir/test.cpp.obj] Error 1
gmake[1]: *** [CMakeFiles/Makefile2:1510: CMakeFiles/test.dir/all] Error 2
gmake: *** [Makefile:91: all] Error 2
// Specify the URL of the file to download
std::string url = "https://api.energidataservice.dk/dataset/Elspotprices";
// Create a string to store the downloaded data
std::string downloadedData;
// Set the URL and callback function
curl_easy_setopt(curl, CURLOPT_URL, url.c_str());
curl_easy_setopt(curl, CURLOPT_WRITEFUNCTION, WriteCallback);
curl_easy_setopt(curl, CURLOPT_WRITEDATA, &downloadedData);
// Perform the request
CURLcode res = curl_easy_perform(curl);
if (res != CURLE_OK) {
std::cerr << "Failed to download the file: " << curl_easy_strerror(res) << std::endl;
}
else {
std::cout << "File downloaded successfully." << std::endl;
// The downloaded file contents are stored in 'downloadedData'
std::cout << "Downloaded Data:\n" << downloadedData << std::endl;
}
Not a Debian heavyweight, but if you don't have it, you need to install the 'build-essentials' package (or something along those lines) as well as the 'devel' package for every relevant package they mention.
On slackware here, I'm finding that file in glibc, so I'd try for a 'glibc-devel' package.
Thanks a lot for taking the time to answer me. All the build-essential I already did (and did again) and it is indeed essential, but it does not fix the problem. I tried your suggestion regarding the glibc and follow the install guidelines here: https://iq.opengenus.org/install-spe...sion-of-glibc/ . Some other stuff were missing on the way, which I also installed and I managed to get glibc installed. Ufortunately the problem is still the same, no features.h found. Any other suggestions?
"The glibc-devel package, also known as libc6-dev in some Linux distributions, contains development libraries and header files for the GNU C Library (glibc). You can download and install this package using your system's package manager. The specific command may vary depending on your Linux distribution."
Unfortunately I have already installed libc6-dev, so I am sill stuck:
oti@raspberrypi:~/pico/itest/build $ sudo apt-get install libc6-dev
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
libc6-dev is already the newest version (2.36-9+rpt2+deb12u3).
libc6-dev set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 19 not upgraded.
The file you wanted was /usr/include/features.h. You appear to have got that from libc6-devel. All the other 'features.h or features.html were unneccessary. When you repeat your compile, does it stick on features.h or some other file? Post the las handful of compile lines.
Here are the last lines:
...
[ 11%] Building CXX object CMakeFiles/itest.dir/itest.cpp.obj
In file included from /usr/include/newlib/wchar.h:16,
from /usr/include/newlib/c++/12.2.1/cwchar:44,
from /usr/include/newlib/c++/12.2.1/bits/postypes.h:40,
from /usr/include/newlib/c++/12.2.1/iosfwd:40,
from /usr/include/newlib/c++/12.2.1/ios:38,
from /usr/include/newlib/c++/12.2.1/ostream:38,
from /usr/include/newlib/c++/12.2.1/iostream:39,
from /home/oti/pico/itest/itest.cpp:1:
/usr/include/aarch64-linux-gnu/sys/cdefs.h:24:11: fatal error: features.h: No such file or directory
24 | # include <features.h>
| ^~~~~~~~~~~~
compilation terminated.
gmake[2]: *** [CMakeFiles/itest.dir/build.make:76: CMakeFiles/itest.dir/itest.cpp.obj] Error 1
gmake[1]: *** [CMakeFiles/Makefile2:1510: CMakeFiles/itest.dir/all] Error 2
gmake: *** [Makefile:91: all] Error 2
And this is the content of the first part of cdefs.h: residing at /usr/include/aarch64-linux-gnu/sys/
/* Copyright (C) 1992-2022 Free Software Foundation, Inc.
Copyright The GNU Toolchain Authors.
This file is part of the GNU C Library.
The GNU C Library is free software; you can redistribute it and/or
modify it under the terms of the GNU Lesser General Public
License as published by the Free Software Foundation; either
version 2.1 of the License, or (at your option) any later version.
The GNU C Library is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
Lesser General Public License for more details.
You should have received a copy of the GNU Lesser General Public
License along with the GNU C Library; if not, see
<https://www.gnu.org/licenses/>. */
#ifndef _SYS_CDEFS_H
#define _SYS_CDEFS_H 1
/* We are almost always included from features.h. */
#ifndef _FEATURES_H
# include <features.h>
#endif
Looking into the folder /usr/include/aarch64-linux-gnu/sys/ where cdefs.h can be found, I notice that there is no such file features.h in the same folder. But is cdefs.h expecting that? It is included as <features.h> and not "features.h", which should mean that it should be looking in the search path. So I looked here:
I looked into all of above search folders, but nowhere there is a file named features.h. BUT I found such file in /usr/include, so I added that search, but still getting the same error:
[ 11%] Building CXX object CMakeFiles/itest.dir/itest.cpp.obj
In file included from /usr/include/newlib/wchar.h:16,
from /usr/include/newlib/c++/12.2.1/cwchar:44,
from /usr/include/newlib/c++/12.2.1/bits/postypes.h:40,
from /usr/include/newlib/c++/12.2.1/iosfwd:40,
from /usr/include/newlib/c++/12.2.1/ios:38,
from /usr/include/newlib/c++/12.2.1/ostream:38,
from /usr/include/newlib/c++/12.2.1/iostream:39,
from /home/oti/pico/itest/itest.cpp:1:
/usr/include/aarch64-linux-gnu/sys/cdefs.h:24:11: fatal error: features.h: No such file or directory
24 | # include <features.h>
| ^~~~~~~~~~~~
compilation terminated.
gmake[2]: *** [CMakeFiles/itest.dir/build.make:76: CMakeFiles/itest.dir/itest.cpp.obj] Error 1
gmake[1]: *** [CMakeFiles/Makefile2:1510: CMakeFiles/itest.dir/all] Error 2
gmake: *** [Makefile:91: all] Error 2
oti@raspberrypi:~/pico/itest/build $ echo $PATH
/usr/include:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games
oti@raspberrypi:~/pico/itest/build $
Then I took this dramatic step:
oti@raspberrypi:/usr/include $ sudo cp features.h /usr/include/aarch64-linux-gnu/sys/features.h
That change something, but now the problem just moved to another file:
[ 11%] Building CXX object CMakeFiles/itest.dir/itest.cpp.obj
In file included from /usr/include/newlib/sys/config.h:5,
from /usr/include/newlib/_ansi.h:11,
from /usr/include/newlib/wchar.h:4,
from /usr/include/newlib/c++/12.2.1/cwchar:44,
from /usr/include/newlib/c++/12.2.1/bits/postypes.h:40,
from /usr/include/newlib/c++/12.2.1/iosfwd:40,
from /usr/include/newlib/c++/12.2.1/ios:38,
from /usr/include/newlib/c++/12.2.1/ostream:38,
from /usr/include/newlib/c++/12.2.1/iostream:39,
from /home/oti/pico/itest/itest.cpp:1:
/usr/include/aarch64-linux-gnu/sys/features.h:392:10: fatal error: features-time64.h: No such file or directory
392 | #include <features-time64.h>
| ^~~~~~~~~~~~~~~~~~~
compilation terminated.
gmake[2]: *** [CMakeFiles/itest.dir/build.make:76: CMakeFiles/itest.dir/itest.cpp.obj] Error 1
gmake[1]: *** [CMakeFiles/Makefile2:1510: CMakeFiles/itest.dir/all] Error 2
gmake: *** [Makefile:91: all] Error 2
oti@raspberrypi:~/pico/itest/build $
I do not think this is the right way to continue??
I've done a bit of this, and /usr/include/ is the spot for headers. So this line
Code:
# include <features.h
is looking for /usr/include/features.h
By the look of things, cdefs.h calls /usr/include/features.h on line 24.
Double check that features.h is there, not zero length, has permissions 0644 and check it's not gibberish. It should be a normal header file. The error message is "No such file or directory"
oti@raspberrypi:/usr/include $ ls -la features.h
-rwxrwxrwx 1 root root 18091 Oct 28 15:38 features.h
oti@raspberrypi:/usr/include $ sudo chmod 0664 features.h
oti@raspberrypi:/usr/include $ ls -la features.h
-rw-rw-r-- 1 root root 18091 Oct 28 15:38 features.h
oti@raspberrypi:/usr/include $ cat features.h
/* Copyright (C) 1991-2022 Free Software Foundation, Inc.
This file is part of the GNU C Library.
The GNU C Library is free software; you can redistribute it and/or
modify it under the terms of the GNU Lesser General Public
License as published by the Free Software Foundation; either
version 2.1 of the License, or (at your option) any later version.
The GNU C Library is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
Lesser General Public License for more details.
You should have received a copy of the GNU Lesser General Public
License along with the GNU C Library; if not, see
<https://www.gnu.org/licenses/>. */
#ifndef _FEATURES_H
#define _FEATURES_H 1
/* These are defined by the user (or the compiler)
to specify the desired environment:
__STRICT_ANSI__ ISO Standard C.
_ISOC99_SOURCE Extensions to ISO C89 from ISO C99.
_ISOC11_SOURCE Extensions to ISO C99 from ISO C11.
_ISOC2X_SOURCE Extensions to ISO C99 from ISO C2X.
__STDC_WANT_LIB_EXT2__
Extensions to ISO C99 from TR 27431-2:2010.
__STDC_WANT_IEC_60559_BFP_EXT__
Extensions to ISO C11 from TS 18661-1:2014.
__STDC_WANT_IEC_60559_FUNCS_EXT__
Extensions to ISO C11 from TS 18661-4:2015.
__STDC_WANT_IEC_60559_TYPES_EXT__
Extensions to ISO C11 from TS 18661-3:2015.
__STDC_WANT_IEC_60559_EXT__
ISO C2X interfaces defined only in Annex F.
_POSIX_SOURCE IEEE Std 1003.1.
_POSIX_C_SOURCE If ==1, like _POSIX_SOURCE; if >=2 add IEEE Std 1003.2;
if >=199309L, add IEEE Std 1003.1b-1993;
if >=199506L, add IEEE Std 1003.1c-1995;
if >=200112L, all of IEEE 1003.1-2004
if >=200809L, all of IEEE 1003.1-2008
_XOPEN_SOURCE Includes POSIX and XPG things. Set to 500 if
Single Unix conformance is wanted, to 600 for the
sixth revision, to 700 for the seventh revision.
_XOPEN_SOURCE_EXTENDED XPG things and X/Open Unix extensions.
_LARGEFILE_SOURCE Some more functions for correct standard I/O.
_LARGEFILE64_SOURCE Additional functionality from LFS for large files.
_FILE_OFFSET_BITS=N Select default filesystem interface.
_ATFILE_SOURCE Additional *at interfaces.
_DYNAMIC_STACK_SIZE_SOURCE Select correct (but non compile-time constant)
MINSIGSTKSZ, SIGSTKSZ and PTHREAD_STACK_MIN.
_GNU_SOURCE All of the above, plus GNU extensions.
_DEFAULT_SOURCE The default set of features (taking precedence over
__STRICT_ANSI__).
_FORTIFY_SOURCE Add security hardening to many library functions.
Set to 1 or 2; 2 performs stricter checks than 1.
_REENTRANT, _THREAD_SAFE
Obsolete; equivalent to _POSIX_C_SOURCE=199506L.
The `-ansi' switch to the GNU C compiler, and standards conformance
options such as `-std=c99', define __STRICT_ANSI__. If none of
these are defined, or if _DEFAULT_SOURCE is defined, the default is
to have _POSIX_SOURCE set to one and _POSIX_C_SOURCE set to
200809L, as well as enabling miscellaneous functions from BSD and
SVID. If more than one of these are defined, they accumulate. For
example __STRICT_ANSI__, _POSIX_SOURCE and _POSIX_C_SOURCE together
give you ISO C, 1003.1, and 1003.2, but nothing else.
These are defined by this file and are used by the
header files to decide what to declare or define:
__GLIBC_USE (F) Define things from feature set F. This is defined
to 1 or 0; the subsequent macros are either defined
or undefined, and those tests should be moved to
__GLIBC_USE.
.......
But it can find it if I include the whole path, but all include files demands the absolute path as well! I spend hours doing that, but there are many many files and I get tired of doing that... Also it should not be necessary..
It seems as the /usr/include PATH is not working, even though I have explicitly put it into the etc/environment also - which I expect that the compiler is using. I have also set my own .bashrc up to include it.. I am a little stuck..
You need to specify the headers path in the Cmake options. I don't know how to do that, but it sounds like Cmake is configuring the Makefile to look in the wrong place for the headers. When the compile starts, make takes it's instructions from the Makefile. But you'd have to change every Makefile in every directory which is a real pain. Look for how to specify that option to Cmake, because I'm not your man for that.
Thanks a lot for your hints. You are right - CMAKE needs to contain the search paths. I have included these and that cures this problem! (unfortunately there is now another problem, but I will create a separate post for that)
Thanks a lot for your hints. You are right - CMAKE needs to contain the search paths. I have included these and that cures this problem! (unfortunately there is now another problem, but I will create a separate post for that)
Thanks!
Br, Ole
Back in the day I did some LFS systems, and that got me familiar with how things worked. I'm still grappling with Cmake, meson & Ninja. What was the magic option that sorted it for you?
Actually it was the fact that CMAKE seemed to ignore the configured PATHs done in linux together with your hint out CMAKE needs to the paths specified instead. And when including these paths, the missing files were found - unfortunately this action seem to generate some funny problems with some declarations no beeing accepted - I have createed a new post for that here and I am also going to create a post in a the CMAKE discourse forum..
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
