public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: perl-Win32-API package problem
Date: Tue, 15 May 2018 19:43:00 -0000	[thread overview]
Message-ID: <87tvr8g271.fsf@Rainer.invalid> (raw)
In-Reply-To: <CAMoHPCY=hMwHco8=quQ0zpvPDw3srMxjzM6v9u-ZcdgQ_6avNw@mail.gmail.com>	(SJ Luo's message of "Sat, 28 Apr 2018 19:41:11 +0800")

SJ Luo writes:
>   The two lines of commands "mv xxxx; cp xxx" are to dereference the
> symbolic links of testing-needed dll files because
> Win32::API::LoadLibrary() seems not be able to resolve Cygwin symbolic
> link.

You'd need to use native symlinks for that to work, yes.

>   By checking the gcc compile option, I found there is a gcc option
> "-fno-stack-protector" provided when I compile this module by myself,
> while the option is removed when I compile with cygport. If I try
> manually compiling without this option, the same problem occurs.

I don't know enough of how the stack protector actually is implemented
to understand why it would work without the protector and stop working
with.

> The host system is Windows7. Cygwin dll is 64bit version 2.10.0-1.
> wish it can be solved soon in next package release.

I'll see if it's possible to remove the option from within cygport, if
yo I'll have to think about any ramifications that might have.


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

SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2018-05-15 19:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-28 11:41 SJ Luo
2018-05-15 19:43 ` Achim Gratz [this message]
2019-09-07 15:11 ` Achim Gratz
2018-05-16 22:28 S.J. Luo

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=87tvr8g271.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --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).