# Compiling 1.9.1 p129 with Borland C++

**URL:** <https://www.ruby-forum.com/t/compiling-1-9-1-p129-with-borland-c/171180>\
**Category:** Ruby\
**Created:** [June 27, 2009, 7:56pm UTC](https://www.ruby-forum.com/t/compiling-1-9-1-p129-with-borland-c/171180 "2009-06-27T19:56:19Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![algnod](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/5f9b8f/32.png) [@algnod](https://www.ruby-forum.com/u/algnod)\
**Post date:** [June 27, 2009, 7:56pm UTC](https://www.ruby-forum.com/t/compiling-1-9-1-p129-with-borland-c/171180/1 "2009-06-27T19:56:19Z")

</div>

The “bcc32”-folder in 1.9.1-p129-source archive is empty. Is there any  
way of compiling this release with the Borland compiler or getting an  
already compiled binary-package?

---

<div class="post-metadata">

**Author:** ![algnod](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/5f9b8f/32.png) [@algnod](https://www.ruby-forum.com/u/algnod)\
**Post date:** [June 27, 2009, 8:36pm UTC](https://www.ruby-forum.com/t/compiling-1-9-1-p129-with-borland-c/171180/2 "2009-06-27T20:36:21Z")

</div>

Alexander Great wrote:

> The “bcc32”-folder in 1.9.1-p129-source archive is empty. Is there any  
> way of compiling this release with the Borland compiler or getting an  
> already compiled binary-package?

I believe the core team abandoned Borland support for 1.9.1 after  
several failed attempts to get somebody to step up to be the official  
maintainer.