Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: Dan Ambrosio via buildroot <buildroot@buildroot.org>
Cc: Dan Ambrosio <dambrosio@outrider.ai>
Subject: Re: [Buildroot] Suspected ccache Issue With wireshark
Date: Thu, 24 Mar 2022 20:35:15 +0100	[thread overview]
Message-ID: <20220324203515.5eeb9584@gmx.net> (raw)
In-Reply-To: <CAAKqzUSn-LBNag6UMxYbzL=1Yi0KgF+9OA0BmgMPN99VOTKJog@mail.gmail.com>

Hello Dan,

On Thu, 24 Mar 2022 09:38:04 -0600, Dan Ambrosio via buildroot <buildroot@buildroot.org> wrote:

> Hello,
> I recently upgraded my buildroot project from 2021.02.6 to the latest
> LTS (2022.02) and ran into a compilation error with the wireshark
> package when BR2_CCACHE is enabled.
>
> It seems like a cmake argument is being passed through to ccache.
>
> >>> wireshark 3.4.12 Building
> PATH="/home/builder/output/oc_general/host/bin:/home/builder/output/oc_general/host/sbin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
>  /usr/bin/make -j17  -C
> /home/builder/output/oc_general/build/wireshark-3.4.12/
> [  0%] Building C object tools/lemon/CMakeFiles/lemon.dir/lemon.c.o
> /home/builder/output/oc_general/host/bin/ccache: invalid option -- 'D'
> Usage:
>     ccache [options]
>     ccache compiler [compiler options]
>     compiler [compiler options]          (via symbolic link)
>
> Common options:
>     -c, --cleanup             delete old files and recalculate size counters
>                               (normally not needed as this is done
>                               automatically)
>     -C, --clear               clear the cache completely (except configuration)
>     -F, --max-files=N         set maximum number of files in cache to N (use 0
>                               for no limit)
>     -M, --max-size=SIZE       set maximum size of cache to SIZE (use 0 for no
>                               limit); available suffixes: k, M, G, T (decimal)
>                               and Ki, Mi, Gi, Ti (binary); default suffix: G
>     -p, --show-config         show current configuration options in
>                               human-readable format
>     -s, --show-stats          show summary of configuration and statistics
>                               counters in human-readable format
>     -z, --zero-stats          zero statistics counters
>
>     -h, --help                print this help text
>     -V, --version             print version and copyright information
>
> Options for scripting or debugging:
>         --dump-manifest=PATH  dump manifest file at PATH in text format
>     -k, --get-config=K        print the value of configuration key K
>         --hash-file=PATH      print the hash (<MD4>-<size>) of the file at PATH
>         --print-stats         print statistics counter IDs and corresponding
>                               values in machine-parsable format
>     -o, --set-config=K=V      set configuration item K to value V
>
> See also <https://ccache.dev>.
> [  0%] Built target cli_main
> make[4]: *** [tools/lemon/CMakeFiles/lemon.dir/build.make:66:
> tools/lemon/CMakeFiles/lemon.dir/lemon.c.o] Error 1
> make[3]: *** [CMakeFiles/Makefile2:10914:
> tools/lemon/CMakeFiles/lemon.dir/all] Error 2
>
> FYI, 2021.02.6 did not exhibit this behavior.

Seems this comes form the configure step:

	[...] /usr/bin/cmake [...] -DLEMON_C_COMPILER=/home/seiderer/Work/Buildroot/build_rpi0w_mesa_v3d_001/host/bin/ccache /usr/bin/gcc [...]


With

--- a/package/wireshark/wireshark.mk
+++ b/package/wireshark/wireshark.mk
@@ -25,7 +25,7 @@ WIRESHARK_CONF_OPTS = \
        -DENABLE_ILBC=OFF \
        -DENABLE_PCAP=ON \
        -DENABLE_SMI=OFF \
-       -DLEMON_C_COMPILER=$(HOSTCC)
+       -DLEMON_C_COMPILER="$(HOSTCC)"

 ifeq ($(BR2_TOOLCHAIN_HAS_LIBATOMIC),y)


this changes to

	[...] /usr/bin/cmake [...] -DLEMON_C_COMPILER="/home/seiderer/Work/Buildroot/build_rpi0w_mesa_v3d_001/host/bin/ccache /usr/bin/gcc" [...]

but the build fails this time with

[...]
cd .../build/wireshark-3.4.12/tools/lemon && "/home/seiderer/Work/Buildroot/build_rpi0w_mesa_v3d_001/host/bin/ccache /usr/bin/gcc" [...]lemon.c

/bin/sh: line 1: .../host/bin/ccache /usr/bin/gcc: No such file or directory


With

--- a/package/wireshark/wireshark.mk
+++ b/package/wireshark/wireshark.mk
@@ -25,7 +25,7 @@ WIRESHARK_CONF_OPTS = \
        -DENABLE_ILBC=OFF \
        -DENABLE_PCAP=ON \
        -DENABLE_SMI=OFF \
-       -DLEMON_C_COMPILER=$(HOSTCC)
+       -DLEMON_C_COMPILER=/usr/bin/gcc

 ifeq ($(BR2_TOOLCHAIN_HAS_LIBATOMIC),y)

The build succeeds...

Regards,
Peter


>
> Thanks,
>
> Dan Ambrosio
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-03-24 19:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-24 15:38 [Buildroot] Suspected ccache Issue With wireshark Dan Ambrosio via buildroot
2022-03-24 19:35 ` Peter Seiderer [this message]
2022-03-24 19:39   ` Peter Seiderer

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=20220324203515.5eeb9584@gmx.net \
    --to=ps.report@gmx.net \
    --cc=buildroot@buildroot.org \
    --cc=dambrosio@outrider.ai \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox