Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15381] New: toolchainfile.cmake.in RELOCATED_HOST_DIR error
Date: Sun, 12 Mar 2023 06:59:09 +0000	[thread overview]
Message-ID: <bug-15381-163@https.bugs.busybox.net/> (raw)

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

            Bug ID: 15381
           Summary: toolchainfile.cmake.in  RELOCATED_HOST_DIR  error
           Product: buildroot
           Version: 2022.02.8
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: major
          Priority: P5
         Component: Other
          Assignee: unassigned@buildroot.uclibc.org
          Reporter: tvirus347@gmail.com
                CC: buildroot@uclibc.org
  Target Milestone: ---

ubuntu22, x64

when my work path is like /home/a/share/buildroot-2022.02.8/.... , then build
cmake package failed:

CMake Error at CMakeLists.txt:51 (project):
  The CMAKE_C_COMPILER:

    /home/a-2022.02.8/output/host/bin/gcc

  is not a full path to an existing compiler tool.

i think this line:
string(REPLACE "/share/buildroot" "" RELOCATED_HOST_DIR
${CMAKE_CURRENT_LIST_DIR})

in
support\misc\toolchainfile.cmake.in

should be:
string(REGEX REPLACE "/share/buildroot$"

-- 
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-03-12  6:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-12  6:59 bugzilla [this message]
2024-06-15 15:06 ` [Buildroot] [Bug 15381] toolchainfile.cmake.in RELOCATED_HOST_DIR error 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-15381-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox