From: "Sören Tempel" <soeren@soeren-tempel.net>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: julien@lepiller.eu, 71925@debbugs.gnu.org
Subject: [bug#71925] [PATCH 2/2] gnu: klee: Build with klee-uclibc support.
Date: Sun, 07 Jul 2024 19:28:52 +0200 [thread overview]
Message-ID: <3OHFY87A45M1V.3QUHDHLCMIAUN@8pit.net> (raw)
In-Reply-To: <9104732dc4c3cd3ee69efbebdf91f695227ba409.camel@gmail.com>
Hello again!
Thanks for the explanation, I send a v2 revision which (hopefully)
addresses your feedback. I have opted to install the libc.a file
to /klee/lib/libc.a this way, it's compatible with search-inputs
without requiring us to patch KLEE's build system.
Let me know what you think :)
Best,
Sören
Liliana Marie Prikler <liliana.prikler@gmail.com> wrote:
> Am Sonntag, dem 07.07.2024 um 18:50 +0200 schrieb Sören Tempel:
> > Hello!
> >
> > Liliana Marie Prikler <liliana.prikler@gmail.com> wrote:
> > > Can we make it so that it uses the file directly instead of
> > > inferring the name? Then we could install klee-uclibc to, say
> > > "/lib/klee/uclibc.a" and reference it in this build by said file
> > > name.
> >
> > That would require us to patch KLEE's CMakeLists.txt and I am not
> > sure if that's worth it [1]. I think I would personally prefer using
> > search-input-file and dirname then. However, I am also still somewhat
> > new to Guix, could you elaborate what the problem with using
> > `(string-append "-DKLEE_UCLIBC_PATH=" #$klee-uclibc)` is (for the
> > sake of expanding my understanding of Guix in this regard)?
> Well, the question is mainly what people ought to do to swap out klee-
> uclibc from their builds – e.g. if they want to replace it with a newer
> one etc. Inputs are our means of making sure that people have a handle
> for this kind of thing.
>
> Cheers
next prev parent reply other threads:[~2024-07-07 17:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-03 19:03 [bug#71925] [PATCH 0/2] Add klee-uclibc soeren
2024-07-03 19:09 ` [bug#71925] [PATCH 1/2] gnu: " soeren
2024-07-06 18:50 ` Liliana Marie Prikler
2024-07-03 19:09 ` [bug#71925] [PATCH 2/2] gnu: klee: Build with klee-uclibc support soeren
2024-07-06 18:49 ` Liliana Marie Prikler
2024-07-07 11:24 ` Sören Tempel
2024-07-07 12:51 ` Liliana Marie Prikler
2024-07-07 16:50 ` Sören Tempel
2024-07-07 16:53 ` Liliana Marie Prikler
2024-07-07 17:28 ` Sören Tempel [this message]
2024-07-07 18:27 ` Liliana Marie Prikler
2024-07-07 19:18 ` Sören Tempel
2024-07-07 17:26 ` [bug#71925] [PATCH v2 1/2] gnu: Add klee-uclibc soeren
2024-07-07 17:26 ` [bug#71925] [PATCH v2 2/2] gnu: klee: Build with klee-uclibc support soeren
2024-07-07 19:19 ` [bug#71925] [PATCH v3 1/2] gnu: Add klee-uclibc soeren
2024-07-07 19:19 ` [bug#71925] [PATCH v3 2/2] gnu: klee: Build with klee-uclibc support soeren
2024-07-08 7:44 ` [bug#71925] [PATCH v4 1/2] gnu: Add klee-uclibc soeren
2024-07-08 7:44 ` [bug#71925] [PATCH v4 2/2] gnu: klee: Build with klee-uclibc support soeren
2024-07-08 8:47 ` [bug#71925] [PATCH 0/2] Add klee-uclibc Sören Tempel
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=3OHFY87A45M1V.3QUHDHLCMIAUN@8pit.net \
--to=soeren@soeren-tempel.net \
--cc=71925@debbugs.gnu.org \
--cc=julien@lepiller.eu \
--cc=liliana.prikler@gmail.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.