[#7043] RUBYOPT versioning? — Caleb Tennis <caleb@...>
Matz, others:
[#7050] RDoc patches for BigDecimal in Ruby CVS — mathew <meta@...>
Now that 1.8.4 is out and the initial flurry of problem reports has died
[#7055] More on VC++ 2005 — Austin Ziegler <halostatue@...>
Okay. I've got Ruby compiling. I'm attempting to get everything in
Hi,
On 05/01/06, nobuyoshi nakada <nobuyoshi.nakada@ge.com> wrote:
On 06/01/06, Austin Ziegler <halostatue@gmail.com> wrote:
Hi,
On 09/01/06, nobuyoshi nakada <nobuyoshi.nakada@ge.com> wrote:
[#7057] 64-bit Solaris READ_DATA_PENDING Revisited — Steven Lumos <steven@...>
[#7078] CRC - a proof-of-concept Ruby compiler — Anders Hkersten <chucky@...>
Hello everyone,
[#7084] mathn: ugly warnings — hadmut@... (Hadmut Danisch)
Hi,
Hadmut Danisch wrote:
Daniel Berger wrote:
*Dean Wampler *<deanwampler gmail.com> writes:
On Fri, 13 Jan 2006, mathew wrote:
On Fri, 13 Jan 2006, Mathieu Bouchard wrote:
ara.t.howard@noaa.gov wrote:
On Fri, 13 Jan 2006, James Britt wrote:
Dean Wampler <deanwampler gmail.com> writes:
On Sat, 14 Jan 2006, mathew wrote:
[#7100] core dump with ruby 1.9.0 (2006-01-10) and bdb-0.5.8 — Tanaka Akira <akr@...17n.org>
I found following test script dumps core.
>>>>> "T" == Tanaka Akira <akr@m17n.org> writes:
In article <200601110905.k0B950Op001713@moulon.inra.fr>,
[#7109] Calling flock with block? — Bertram Scharpf <lists@...>
Hi,
On Thu, 12 Jan 2006, Bertram Scharpf wrote:
[#7129] YAML.load({[]=>""}.to_yaml) — Tanaka Akira <akr@...17n.org>
I found that current YAML doesn't round trip {[]=>""}.
Hi.
Hi.
In article <20060115202203.D3624CA0.ocean@m2.ccsnet.ne.jp>,
[#7162] FileUtils.mv does not unlink source file when moving over filesystem boundary — Pav Lucistnik <pav@...>
Hi,
On Mon, 16 Jan 2006, Pav Lucistnik wrote:
[#7178] Add XHTML 1.0 Output Support to Ruby CGI — Paul Duncan <pabs@...>
The attached patch against Ruby 1.8.4 adds XHTML 1.0 output support to
[#7186] Ruby 1.9 and FHS — "Kirill A. Shutemov" <k.shutemov@...>
Build and install system changes:
[#7195] trouble due ruby redefining posix function eaccess — noreply@...
Bugs item #3317, was opened at 2006-01-24 15:33
[#7197] SSL-enabled DRb fds on SSLError? — ctm@... (Clifford T. Matthews)
Howdy,
On Jan 24, 2006, at 12:46 PM, Clifford T. Matthews wrote:
Patch worked fine against HEAD.
[#7203] bcc32's memory manager bug — "H.Yamamoto" <ocean@...2.ccsnet.ne.jp>
Hi.
[#7211] Some troubles with an embedded ruby interpreter — Matt Mower <matt.mower@...>
Hi folks,
[#7216] String#scan loops forefever if scanned string is modified inside block. — noreply@...
Bugs item #3329, was opened at 2006-01-26 10:55
[#7226] Fwd: Re: Question about massive API changes — "Sean E. Russell" <ser@...>
Hello,
Sean E. Russell wrote:
>
On 1/28/06, Caleb Tennis <caleb@aei-tech.com> wrote:
On Saturday 28 January 2006 17:13, Wilson Bilkovich wrote:
Sean E. Russell wrote:
[#7249] PATCH: append option to sysread — Yohanes Santoso <ysantoso-rubycore@...>
[#7259] TCP/UDP server weird lags on 1.8.4 linux — "Bill Kelly" <billk@...>
Hi !
More on VC++ 2005
Okay. I've got Ruby compiling. I'm attempting to get everything in
place, but there are a couple of issues to resolve still.
1. The zlib team recommends that you only compile to zlib1.dll if you
are linking against msvcrt.dll, because of zlib's intended status as a
"system component". As such, I am creating ruby-zlib1.dll. How can I
tell Ruby that's the version of zlib to compile against for zlib.so?
This applies to OpenSSL as well.
2. The dynamic discovery of DLLs is harder. It is possible to put
msvcr80.dll in the Ruby bin/ directory, but it is not the recommended
way to do it, since msvcr80.dll is intended to be an SxS
(side-by-side) assembly. I have made modifications to the Zlib and
OpenSSL build processes (and now pdcurses, too) to make this happen,
but the Ruby build process is a little too... confusing to me to deal
with. Basically, there's a link step and a post-link step. After the
link is done, a .manifest file is generated, e.g.:
ruby.exe
ruby.exe.manifest
msvcr80-ruby18.dll
msvcr80-ruby18.dll.manifest
Don't ask my *why*, but the linker doesn't give the ability to
automatically embed the manifest in the DLL or the EXE. However, there
is a way to do it using mt ("manifest tool").
mt -nologo -manifest ruby.exe.manifest -outputresource:ruby.exe;1
mt -nologo -manifest msvcr80-ruby18.dll.manifest
-outputresource:msvcr80-ruby18.dll;2
In [n]make terms, that's:
mt -nologo $@.manifest -outputresource:$@;1 # for .exe only
mt -nologo $@.manifest -outputresource:$@;2 # for .dll only
There's a more complex step available that supports incremental
builds, but I don't think that's the way that we want to or need to
deal with it, to be honest.
Without this step, the installer must install not only the .exe or
.dll, but the .manifest file along with it. With this step, the
installer needs be made no smarter and binaries just work the way they
always have on Windows.
I really hate to ask, in some ways, but what exactly do I have to do
to get this stuff to work?
Thanks,
-austin
--
Austin Ziegler * halostatue@gmail.com
* Alternate: austin@halostatue.ca