public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: question for perl maintainer
Date: Fri, 08 Jul 2005 17:53:00 -0000	[thread overview]
Message-ID: <20050708175353.GL7507@calimero.vinschen.de> (raw)
In-Reply-To: <42CEBBDE.5080009@familiehaase.de>

On Jul  8 19:46, Gerrit P. Haase wrote:
> Corinna Vinschen wrote:
> >What? Why?  OpenSSL uses another base address already in the Makefile
> >(0x63000000).
> 
> Good thing.  I had problems using openssl extensions for MySQL and perl
> together (half year back).  Is this a recent change or was it only perl
> failing?

OpenSSL 0.9.7 uses 0xFE000000 as base address.  For some reason which
is entirely beyond me, the OpenSSL developers chose 0x61000000 (OUCH!)
as base address for 0.9.8, which is especially funny because this base
address is *only* used for the Cygwin build.  I vetoed the address and
let it change to 0x63000000 for 0.9.8.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          mailto:cygwin@cygwin.com
Red Hat, Inc.

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

  reply	other threads:[~2005-07-08 17:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-07 17:10 Perl Win32::Shortcut screws up fork Adye, TJ (Tim)
     [not found] ` <7231C15EAC2F164CA6DC326D97493C8BA1C3F1@exchange35.fed.cclr  c.ac.uk>
2005-07-07 18:09   ` Larry Hall
2005-07-07 18:29     ` question for perl maintainer Christopher Faylor
2005-07-07 20:47       ` Gerrit P. Haase
2005-07-07 21:12         ` Gerrit P. Haase
2005-07-07 21:50           ` Christopher Faylor
2005-07-08  9:53             ` Gerrit P. Haase
2005-07-08 12:27               ` Christopher Faylor
2005-07-08 15:22                 ` Gerrit P. Haase
2005-07-08 17:27                   ` Corinna Vinschen
2005-07-08 17:47                     ` Gerrit P. Haase
2005-07-08 17:53                       ` Corinna Vinschen [this message]
     [not found]                     ` <20050708173253.GG18981@trixie.casa.cgf.cx>
     [not found]                       ` <0add01c583e4$6d667320$3e0010ac@wirelessworld.airvananet.com>
     [not found]                         ` <20050708180417.GK18981@trixie.casa.cgf.cx>
     [not found]                           ` <20050711130656.GD3856@tishler.net>
     [not found]                             ` <0bdb01c5861d$429e2080$3e0010ac@wirelessworld.airvananet.com>
     [not found]                               ` <20050711134355.GG3856@tishler.net>
     [not found]                                 ` <42D28927.7010401@familiehaase.de>
     [not found]                                   ` <20050711150703.GA444@tishler.net>
2005-07-11 22:55                                     ` Observation for ALL maintainers who provide dlls (was Re: question for perl maintainer) Gerrit P. Haase
2005-07-11 12:30           ` question for perl maintainer Jason Tishler
2005-07-07 21:49         ` Christopher Faylor

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=20050708175353.GL7507@calimero.vinschen.de \
    --to=corinna-cygwin@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).