From: sboisvert@gydle.com (Sebastien Boisvert)
Subject: [lttng-dev] Building URCU in a Cygwin 64 environment
Date: Tue, 31 May 2016 09:39:10 -0400 [thread overview]
Message-ID: <574D93FE.7000703@gydle.com> (raw)
Hi,
I am in the process of writing a blog article on the use of the LTTng-UST userspace event tracer on Windows.
I am building urcu and LTTng-UST in a Cygwin 64 environment. Then, I plan to use LTTng in Visual Studio Community, so I mostly need headers (.h) and shared libraries (.dll).
When I am building urcu (0.9.2), I get this message:
libtool: link: warning: undefined symbols not allowed in x86_64-unknown-cygwin shared libraries
The immediate consequence seems to be the absence of .dll files in the urcu build that I am generating. Otherwise, the build contains static library files and headers.
However, I suppose that the .a static library files also have undefined symbols as I am getting linking issues when building LTTng-UST.
Do you have a clue of what may be the issue here ? Otherwise, I will continue my investigation and get around the issue eventually.
next reply other threads:[~2016-05-31 13:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 13:39 Sebastien Boisvert [this message]
2016-05-31 14:47 ` Jonathan Rajotte Julien
2016-05-31 15:12 ` Sebastien Boisvert
2016-05-31 21:52 ` Mathieu Desnoyers
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=574D93FE.7000703@gydle.com \
--to=sboisvert@gydle.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