November 05, 2013
On 11/5/2013 4:02 AM, Iain Buclaw wrote:
> There's only one file named readme.txt.  ;-)
>
> See here for the latest file:
> https://github.com/D-Programming-Language/dmd/blob/master/src/readme.txt

Thanks, I'll take care of it.

November 05, 2013
On 2013-11-05 10:09, Walter Bright wrote:

> Why not volunteer to handle the FreeBSD package builds?

Hmm, turns out it's currently not possible to build C++ code for 32bit on a 64bit FreeBSD machine. This might take a bit longer than I expected. I can still send you 64bit binaries if that is of interest.

-- 
/Jacob Carlborg
November 05, 2013
On 11/5/2013 1:50 PM, Jacob Carlborg wrote:
> On 2013-11-05 10:09, Walter Bright wrote:
>
>> Why not volunteer to handle the FreeBSD package builds?
>
> Hmm, turns out it's currently not possible to build C++ code for 32bit on a
> 64bit FreeBSD machine. This might take a bit longer than I expected. I can still
> send you 64bit binaries if that is of interest.


Yeah, you essentially need both a 32 bit FreeBSD install and a 64 bit one.

I suppose what's needed is a "one click install" package for FreeBSD.
November 05, 2013
On 11/5/2013 1:52 AM, Arjan wrote:
>> Why not volunteer to handle the FreeBSD package builds?
>
> I have access to FreeBSD machine(s) and willing to lend a hand and spend some
> time on this.
> What is needed to do the FreeBSD package build?
> (Currently I just do a git clone/pull of the github dlang stuff and build it to
> get the master or any other branch I want)
> Were do I find the build and package instructions?

That's part of handling it - figuring out all that stuff :-) I don't know what it is.

> Is running regressions tests required before releasing a build package?

Yes, and the regression suite is part of the github repository. Alternatively, you could talk to Brad and get the actual binaries from the autotester.

> What is the packages release (and build) frequency?

It's a bit erratic, but generally once every 3 months or so.


> DMD1 and DMD2 (and GDC) seems to be in the FreeBSD ports collection. Why can't
> those be used to buid the packages?

Building it is less of an issue than getting a FreeBSD install.
November 05, 2013
On 11/5/13 2:00 PM, Walter Bright wrote:
> On 11/5/2013 1:52 AM, Arjan wrote:
>>> Why not volunteer to handle the FreeBSD package builds?
>>
>> I have access to FreeBSD machine(s) and willing to lend a hand and spend some
>> time on this.
>> What is needed to do the FreeBSD package build?
>> (Currently I just do a git clone/pull of the github dlang stuff and build it to
>> get the master or any other branch I want)
>> Were do I find the build and package instructions?
>
> That's part of handling it - figuring out all that stuff :-) I don't know what it is.
>
>> Is running regressions tests required before releasing a build package?
>
> Yes, and the regression suite is part of the github repository. Alternatively, you could talk to
> Brad and get the actual binaries from the autotester.
>
>> What is the packages release (and build) frequency?
>
> It's a bit erratic, but generally once every 3 months or so.
>
>
>> DMD1 and DMD2 (and GDC) seems to be in the FreeBSD ports collection. Why can't
>> those be used to buid the packages?
>
> Building it is less of an issue than getting a FreeBSD install.

I really do intend to get the package builder producing bundles (not for every single build, that'd be.. scary).  It's on my todo list.  Maybe I'll dedicate my christmas vacation to that project.
November 05, 2013
On 11/5/2013 2:10 PM, Brad Roberts wrote:
> I really do intend to get the package builder producing bundles (not for every
> single build, that'd be.. scary).  It's on my todo list.  Maybe I'll dedicate my
> christmas vacation to that project.

That would be awesome, and would be a big step forward in getting a reliable release process.
November 05, 2013
On 11/5/13 2:10 PM, Brad Roberts wrote:
> I really do intend to get the package builder producing bundles (not for
> every single build, that'd be.. scary).  It's on my todo list.  Maybe
> I'll dedicate my christmas vacation to that project.

That would be awesome!!

Andrei
November 06, 2013
On Tuesday, 5 November 2013 at 21:58:38 UTC, Walter Bright wrote:
> On 11/5/2013 1:50 PM, Jacob Carlborg wrote:
>> On 2013-11-05 10:09, Walter Bright wrote:
>>
>>> Why not volunteer to handle the FreeBSD package builds?
>>
>> Hmm, turns out it's currently not possible to build C++ code for 32bit on a
>> 64bit FreeBSD machine. This might take a bit longer than I expected. I can still
>> send you 64bit binaries if that is of interest.
>
>
> Yeah, you essentially need both a 32 bit FreeBSD install and a 64 bit one.
>
> I suppose what's needed is a "one click install" package for FreeBSD.

You can compile 32-bit code on a 64-bit FreeBSD machine, as long as you do it inside a 32-bit FreeBSD jail.  I've done this many times when compiling 32-bit FreeBSD packages and it works fine.  If Jacob is interested, all he needs to do is setup a 32-bit FreeBSD jail, which is pretty straightforward.

On Tuesday, 5 November 2013 at 09:52:26 UTC, Arjan wrote:
> DMD1 and DMD2 (and GDC) seems to be in the FreeBSD ports collection. Why can't those be used to buid the packages?

The gdc FreeBSD port is marked as broken and deprecated.  I don't think it's been updated in years, back when gdc was still written by the original author.

I wrote the original makefiles for dmd1 and dmd2.  They still work, but the current maintainer usually doesn't bother doing more than a cursory version number bump, so they'll often uninstall cleanly, as the list of files installed will be wrong (ie the pkg-plist is outdated).  I also wrote a ldc1 makefile back then, but nobody maintained it, so it has been removed.

It appears that dlang builds their own packages for some platforms, regardless of whether it's in the native package repository or not.  Probably a good idea, for instant gratification of those who want to try it out.
November 06, 2013
On 2013-11-06 07:26, Joakim wrote:

> You can compile 32-bit code on a 64-bit FreeBSD machine, as long as you
> do it inside a 32-bit FreeBSD jail.  I've done this many times when
> compiling 32-bit FreeBSD packages and it works fine. If Jacob is
> interested, all he needs to do is setup a 32-bit FreeBSD jail, which is
> pretty straightforward.

Yeah, I noticed that's an alternative. But since I've never done that
that's way I said "might take a bit longer than I expected".

Apparently it can generate 32bit binaries just fine, the problem is some header files are not properly ported to handle both 32 and 64bit. A C Hello World application works without a jail. As well as any D application (at least the one I tried).

Seems Mac OS X is the only platform that handles this well, due to the use of universal binaries.

-- 
/Jacob Carlborg
1 2 3 4 5
Next ›   Last »