all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: Greg Hogan <code@greghogan.com>
Cc: 59342@debbugs.gnu.org
Subject: [bug#59342] [PATCH 2/3] gnu: lldb: Update to 15.0.5.
Date: Sat, 19 Nov 2022 13:34:15 +0000	[thread overview]
Message-ID: <87pmdjawz7.fsf@cbaines.net> (raw)
In-Reply-To: <f9add8538ba8507141ab5861f9f266439a5f1cfc.1668714905.git.code@greghogan.com>

[-- Attachment #1: Type: text/plain, Size: 832 bytes --]


Greg Hogan <code@greghogan.com> writes:

> * gnu/packages/llvm.scm (lldb): Update to 15.0.5.
> [version]: Use version from LLVM-15.
> [inputs]: Change from LLVM-14 and CLANG-14 to LLVM-15 and CLANG-15.
> ---
>  gnu/packages/llvm.scm | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/gnu/packages/llvm.scm b/gnu/packages/llvm.scm
> index 020c9bb302..d9bbe9c078 100644
> --- a/gnu/packages/llvm.scm
> +++ b/gnu/packages/llvm.scm
> @@ -1631,7 +1631,7 @@ (define-public lld-as-ld-wrapper
>  (define-public lldb
>    (package
>      (name "lldb")
> -    (version "14.0.6")
> +    (version (package-version llvm-15))

Hi Greg, thanks for the patches.

Looking at https://qa.guix.gnu.org/issue/59342 it seems that this
updated lldb@15.0.5 fails to build.

Do you see the same failure locally?

Thanks,

Chris

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]

  reply	other threads:[~2022-11-19 13:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-17 20:03 [bug#59342] [PATCH 0/3] Update lldb Greg Hogan
2022-11-17 20:06 ` [bug#59342] [PATCH 1/3] gnu: LLVM, Clang, libomp, lld: Update to 15.0.5 Greg Hogan
2022-11-17 20:06 ` [bug#59342] [PATCH 2/3] gnu: lldb: " Greg Hogan
2022-11-19 13:34   ` Christopher Baines [this message]
2022-11-21 14:35     ` Greg Hogan
2022-11-22  9:39       ` Christopher Baines
2022-11-17 20:06 ` [bug#59342] [PATCH 3/3] gnu: libcxx: " Greg Hogan

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=87pmdjawz7.fsf@cbaines.net \
    --to=mail@cbaines.net \
    --cc=59342@debbugs.gnu.org \
    --cc=code@greghogan.com \
    /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. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

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.