Re: bugs when building openwrt linux 18.06

Bernhard Voelker <[email protected]>
Newsgroups gmane.comp.gnu.findutils.bugs
Message-ID <[email protected]>
On 2/26/21 3:20 AM, Lachlan Peter wrote:
> Building Linux for Omega Onion with Openwrt and get the bugs listed in the
> attached document.
> 
> The setup uses Ubuntu 20.04.2 LTS x64 on intel i5 and the following steps
> $ git clone https://github.com/OnionIoT/source.git                 // get
> source
> $ cd source
> $ sh scripts/onion-feed-setup.sh
>  // setup feeds
> $ rm -r ./package/feeds/onion/transmission-console-app     // creates
> errors - remove
> $ rm -r ./package/feeds/onion/zeromq                                  //
> creates errors - remove
> $ python scripts/onion-setup-build.py                                  //
> setup build
> $ vi /usr/include/asm-generic/int-ll64.h
>       Edit line 31    to prevent errors:
>                             from: __extension__ typedef unsigned long long
> __64;
>                             to:   typedef uint64_t __64;

Really? Change the host's header files? Sounds crude.

> $ make -j1 V=s

sorry, I don't get past this error on my system:

  Build dependency: Please install the GNU C Compiler (gcc) 4.8 or later \
    gcc -dumpversion | grep -E '^(4\.[8-9]|[5-9]\.?)'
  Build dependency: Please install the GNU C++ Compiler (g++) 4.8 or later \
    gcc -dumpversion | grep -E '^(4\.[8-9]|[5-9]\.?)'

  Prerequisite check failed. Use FORCE=1 to override.

Passing the suggested FORCE=1 doesn't help either.

Looking at the 'README.md' file, it seems that compiling on any arbitrary
Linux system is not the preferred way:

  There are two preferred ways to use the buildsystem:

  1. Using the `onion/omega2-source` Docker image **Recommended method**
  2. Running the build system on a Linux system

Compiling via docker as described in that README.md works here as expected.

> Final output is:
> checking for BEOS mounted file system support functions... no
> checking whether it is possible to resort to fread on /etc/mnttab... no
> configure: error: could not determine how to read list of mounted file
> systems

The terminal output of the failed build doesn't tell us too much.
Please look into 'config.log'.

I didn't look deeper in the scripting around the plain findutils build,
but as I can't reproduce the error, and given that the building is not quite
standard, I guess you could get better help from the people/distribution
who maintain OnionIoT.

> make[3]: *** [Makefile:22:
> /home/lachlan/omega/source/build_dir/host/findutils-4.6.0/.configured]
> Error 1
> make[3]: Leaving directory '/home/lachlan/omega/source/tools/findutils'
> Command exited with non-zero status 2
> time: tools/findutils/compile#25.09#7.82#59.48
> make[2]: *** [tools/Makefile:154: tools/findutils/compile] Error 2

Finally, findutils-4.6.0 is from Dec 2015.  I suggest updating to 4.8.0 instead.

Have a nice day,
Berny
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.