All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15805] New: Unable to build with ccache enabled.
Date: Mon, 25 Sep 2023 22:02:11 +0000	[thread overview]
Message-ID: <bug-15805-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=15805

            Bug ID: 15805
           Summary: Unable to build with ccache enabled.
           Product: buildroot
           Version: 2023.05.2
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned@buildroot.uclibc.org
          Reporter: paul@modernsubject.com
                CC: buildroot@uclibc.org
  Target Milestone: ---

Created attachment 9643
  --> https://bugs.busybox.net/attachment.cgi?id=9643&action=edit
cmake error log

When building with ccache enabled, I get the following error during the ccache
build:

"
... snip
-- Ccache version: 4.7.4                                                        
-- Ccache dev mode: OFF                                                         
-- Performing Test std_atomic_without_libatomic                                 
-- Performing Test std_atomic_without_libatomic - Success                       
-- Performing Test std_filesystem_without_libfs                                 
-- Performing Test std_filesystem_without_libfs - Failed                        
-- Performing Test std_filesystem_with_libfs                                    
-- Performing Test std_filesystem_with_libfs - Failed                           
CMake Error at cmake/StdFilesystem.cmake:22 (message):                          
  Toolchain doesn't support std::filesystem with nor without -lstdc++fs         
Call Stack (most recent call first):                                            
  cmake/StandardSettings.cmake:57 (include)                                     
  CMakeLists.txt:70 (include)                                                   


-- Configuring incomplete, errors occurred!                                     
See also
"/home/paul/src/pi2/buildroot/build/host-ccache-4.7.4/CMakeFiles/CMakeOutput.lo 
g".                                                                             
See also
"/home/paul/src/pi2/buildroot/build/host-ccache-4.7.4/CMakeFiles/CMakeError.log 
".                                                                              
make[1]: *** [package/pkg-generic.mk:283:
/home/paul/src/pi2/buildroot/build/host-ccache 
-4.7.4/.stamp_configured] Error 1                                               
make: *** [Makefile:23: _all] Error 2 
"

Disabling ccache, everything builds properly.  Also 2023.02.4 builds properly
with ccache.  I also tried building with "BR2_FORCE_HOST_BUILD=y" -- no change.

Environment:
- openSUSE Leap 15.5

Target:
- Raspberry Pi 2

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2023-09-25 22:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-25 22:02 bugzilla [this message]
2023-09-25 22:03 ` [Buildroot] [Bug 15805] Unable to build with ccache enabled bugzilla
2024-06-15 15:13 ` bugzilla

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=bug-15805-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@uclibc.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.