public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: Perl and crypt.h
Date: Tue, 24 Nov 2015 18:58:00 -0000	[thread overview]
Message-ID: <87r3jfusvt.fsf@Rainer.invalid> (raw)
In-Reply-To: <564C5A1A.1070001@asokolov.org> (Alexey Sokolov's message of	"Wed, 18 Nov 2015 10:59:38 +0000")

Alexey Sokolov writes:
> I think perl package should depend on libcrypt-devel on x86_64.

Most definitely not.  If anything there would need to be a perl-devel
package that pulls stuff like that in.

> Otherwise, here's error while embedding perl:
>
>> In file included from /usr/lib/perl5/5.22/x86_64-cygwin-threads/CORE/op.h:635:0,
>>                  from /usr/lib/perl5/5.22/x86_64-cygwin-threads/CORE/perl.h:3736,
>>                  from /home/q/KVIrc/src/modules/perlcore/libkviperlcore.cpp:68:
>> /usr/lib/perl5/5.22/x86_64-cygwin-threads/CORE/reentr.h:104:26: fatal error: crypt.h: No such file or directory
>>  #       include <crypt.h>
>>                           ^
>
> It seems to works without libcrypt-devel on i686 though.

This is packaged differently for x86 and x86_64 and part of the crypt
package on x86 (library and development files not separated).  It would
be nice if it was using the same packaging on both architectures.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Wavetables for the Terratec KOMPLEXER:
http://Synth.Stromeko.net/Downloads.html#KomplexerWaves

      reply	other threads:[~2015-11-24 18:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-18 10:59 Alexey Sokolov
2015-11-24 18:58 ` Achim Gratz [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=87r3jfusvt.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --cc=cygwin-apps@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).