Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: Michael Jeanson via lttng-dev <lttng-dev@lists.lttng.org>
To: "Seidl, Aron" <aron.seidl@zeiss.com>,
	"lttng-dev@lists.lttng.org" <lttng-dev@lists.lttng.org>
Subject: Re: [lttng-dev] Building the Babeltrace-Libary for Windows?
Date: Tue, 7 Nov 2023 10:57:13 -0500	[thread overview]
Message-ID: <191bdafa-e05e-4925-91a6-62c511d10744@efficios.com> (raw)
In-Reply-To: <AM9P190MB10759C317F92C6DF8CE429B688AAA@AM9P190MB1075.EURP190.PROD.OUTLOOK.COM>

On 2023-11-06 02:43, Seidl, Aron wrote:
> Hi Michael,
> 
> Thank you a lot for your answer! I think I can work with that.
> 
> I set up the msys64 environment with all the packages that I need to build, except for glibc. I ran the script and as always does the build process fail because I can't install glibc in this environment.
> Even building glibc from source fails, because the system is not compatible.
> 
> Do you guys link babeltrace to a different C library when building on windows, or is there a way for a possible workaround?
> I'd be super grateful for a little more help!
> 
> I wish you a nice day
> 
> Sincerely,
> Aron

Hi Aron,

I would need a lot more details on what your are doing and what the failure is 
to be able to help you. As for the libc, it is provided in the base MSYS2 
environment, you shouldn't need to install it.

Michael

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

      reply	other threads:[~2023-11-07 15:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-03 11:48 Seidl, Aron via lttng-dev
2023-11-03 14:21 ` Michael Jeanson via lttng-dev
2023-11-06  7:43   ` Seidl, Aron via lttng-dev
2023-11-07 15:57     ` Michael Jeanson via lttng-dev [this message]

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=191bdafa-e05e-4925-91a6-62c511d10744@efficios.com \
    --to=lttng-dev@lists.lttng.org \
    --cc=aron.seidl@zeiss.com \
    --cc=mjeanson@efficios.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox