Go to file
Yann E. MORIN 590d89fdad package/file: fix build with gcc-4.8
file-5.41 uses AC_PROG_CC, and was generated with autoconf 2.69. That
oldish version of autoconf does not check the C standard when AC_PROG_CC
is called, and standard-specific macros must be called instead:
AC_PROG_CC_C89, AC_PROG_CC_C99, or AC_PROG_CC_STDC.

So we would need to patch configure.ac to call either of those options,
and then we'd have to autoreocnf.

However, that would autoreconf with our autoconf, version 2.71. In that
version, AC_PROG_CC always check what C standards are available and sets
the appropriate ac_cv_XXX variables, and the previous macros,
AC_PROG_CC_C89, AC_PROG_CC_C99, and AC_PROG_CC_STDC are deprecated.

So it turns out that we just need to autoreconf.

Fixes:
  - http://autobuild.buildroot.org/results/9e7868be00f2cd18205b2ce664be95f8b9e2b063
  - http://autobuild.buildroot.org/results/31cbc313fceb84c0cbb1969fca5ac44244871dbc

Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
Cc: Fabrice Fontaine <fontaine.fabrice@gmail.com>
2022-01-08 22:48:16 +01:00
arch
board configs/olimex_a20_olinuxino: fix mali not working because Linux version >= 4.20 2022-01-08 21:56:55 +01:00
boot
configs configs/olimex_stmp157: bump U-Boot version 2022-01-08 15:49:15 +01:00
docs
fs
linux
package package/file: fix build with gcc-4.8 2022-01-08 22:48:16 +01:00
support package/lua-inotify: new package 2022-01-08 18:03:59 +01:00
system
toolchain toolchain/toolchain-wrapper: reproducible builds: omit absolute paths from debug symbols 2022-01-08 14:48:22 +01:00
utils
.clang-format
.defconfig
.flake8
.gitignore
.gitlab-ci.yml
CHANGES
Config.in
Config.in.legacy package/civetweb: drop BR2_PACKAGE_CIVETWEB_WITH_LUA 2022-01-08 20:26:07 +01:00
COPYING
DEVELOPERS package/sdbus-cpp: new package 2022-01-08 21:58:32 +01:00
Makefile
Makefile.legacy
README

Buildroot is a simple, efficient and easy-to-use tool to generate embedded
Linux systems through cross-compilation.

The documentation can be found in docs/manual. You can generate a text
document with 'make manual-text' and read output/docs/manual/manual.text.
Online documentation can be found at http://buildroot.org/docs.html

To build and use the buildroot stuff, do the following:

1) run 'make menuconfig'
2) select the target architecture and the packages you wish to compile
3) run 'make'
4) wait while it compiles
5) find the kernel, bootloader, root filesystem, etc. in output/images

You do not need to be root to build or run buildroot.  Have fun!

Buildroot comes with a basic configuration for a number of boards. Run
'make list-defconfigs' to view the list of provided configurations.

Please feed suggestions, bug reports, insults, and bribes back to the
buildroot mailing list: buildroot@buildroot.org
You can also find us on #buildroot on OFTC IRC.

If you would like to contribute patches, please read
https://buildroot.org/manual.html#submitting-patches