From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: clang dependencies
Date: Tue, 13 Feb 2018 23:35:00 -0000 [thread overview]
Message-ID: <5aa58de2-921e-ebfc-4134-0c4dbeda0367@cygwin.com> (raw)
In-Reply-To: <VI1PR0302MB339163B88EF35C501BC46ADBA0F60@VI1PR0302MB3391.eurprd03.prod.outlook.com>
[-- Attachment #1.1: Type: text/plain, Size: 1229 bytes --]
On 2018-02-13 12:07, Alberto Escrig Vidal wrote:
> Consider the following program:
> #include <iostream>
> int main() {}
>
> If I compile it with
> clang++ -stdlib=libc++ foo.cpp
> i get the error:
> /usr/include/c++/v1/locale:197:10: fatal error: 'nl_types.h' file not found
> #include <nl_types.h>
>
> The reason is that libcatgets-devel 1.1-2 was obsoleted by cygwin-devel.
It sounds like you did not update cygwin/cygwin-devel and
catgets/libcatgets-devel in sync. Could you check:
$ cygcheck -c cygwin cygwin-devel
Cygwin Package Information
Package Version Status
cygwin 2.10.0-1 OK
cygwin-devel 2.10.0-1 OK
If either those say Incomplete instead of OK -- which I suspect at least
cygwin-devel will -- then reinstall that/those package(s).
> On the other hand, if I compile it with:
> clang++ -stdlib=libc++ foo.cpp
You mean clang++ -stdlib=libstdc++ here?
> it fails to link via gcc because -liconv is missing, yet I got libiconv installed.> I had to manually install libiconv-dev for libiconv.a to be in /usr/lib/.
libiconv-devel should have been pulled in by something else, but I'll
have to take a look.
--
Yaakov
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2018-02-13 23:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-13 18:07 Alberto Escrig Vidal
2018-02-13 23:35 ` Yaakov Selkowitz [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=5aa58de2-921e-ebfc-4134-0c4dbeda0367@cygwin.com \
--to=yselkowitz@cygwin.com \
--cc=cygwin@cygwin.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).