It is still not possible to use D on debian/ubuntu (page 2)

On Monday, 2 January 2017 at 01:24:58 UTC, Nordlöw wrote: > On Sunday, 1 January 2017 at 23:55:37 UTC, deadalnix wrote: >> But it is not clear if anyone cares at this stage... > > 2.072.2 was released yesterday. Doesn't that work on Ubuntu 16.10? Victory ! It took some time but here we are. Good to see this is fixed. Thanks whoever fixed it!

On Monday, 2 January 2017 at 11:15:41 UTC, Russel Winder wrote: > On Mon, 2017-01-02 at 01:06 +0000, deadalnix via Digitalmars-d wrote: >> > […] >> On a broader note, all my project involving D are on standby since this problem occurred. I'd be a business, this'd be the time where I would put D into the trash, use something else and never look back. > > Just use LDC? No. I'd be then stuck with other bugs which would also require month to be fixed.

On Monday, 2 January 2017 at 01:24:58 UTC, Nordlöw wrote: > 2.072.2 was released yesterday. Doesn't that work on Ubuntu 16.10? I automate installation of DMD with https://github.com/nordlow/scripts/blob/master/pget_dmd-stable which was just updated to latest stable

On Sunday, 1 January 2017 at 23:55:37 UTC, deadalnix wrote: > But it is not clear if anyone cares at this stage... It's fairly embarrassing to read so much uninformed noise. https://trello.com/c/E1LU0SAe/269-issue-16794-deb-not-working-on-ubuntu-16-10-because-of-default-pie-linking (added 5 days after bug report) http://forum.dlang.org/post/o3ogr0$27hu$1@digitalmars.com https://issues.dlang.org/show_bug.cgi?id=16794

On Monday, 2 January 2017 at 02:31:16 UTC, H. S. Teoh wrote: > On Sun, Jan 01, 2017 at 11:55:37PM +0000, deadalnix via Digitalmars-d wrote: >> But it is not clear if anyone cares at this stage... > > I care. But I've been using custom-built DMD on Debian, and it has been working so far. > > Of course, I don't know about the .deb distribution. A fix was recently pushed, but I don't know if that fixed the problem. My solution was basically to built druntime & phobos with -fPIC so that static libphobos.a is PIC. But my solution was declined in bugzilla and a different fix was opted for. Linking against shared phobos was just mentioned as immediate workaround. Changing over to -fPIC by default amd64 was one of multiple options that had to be carefully evaluated. It's fairly trivial to just demand a certain change without considering it's impact.

January 02, 2017

Re: It is still not possible to use D on debian/ubuntu

Posted by Basile B.
in reply to Martin Nowak

Permalink

Basile B.

Posted in reply to Martin Nowak

Permalink

On Monday, 2 January 2017 at 13:58:53 UTC, Martin Nowak wrote:
> On Monday, 2 January 2017 at 02:31:16 UTC, H. S. Teoh wrote:
>> On Sun, Jan 01, 2017 at 11:55:37PM +0000, deadalnix via Digitalmars-d wrote:
>>> But it is not clear if anyone cares at this stage...
>>
>> I care. But I've been using custom-built DMD on Debian, and it has been working so far.
>>
>> Of course, I don't know about the .deb distribution. A fix was recently pushed, but I don't know if that fixed the problem.  My solution was basically to built druntime & phobos with -fPIC so that static libphobos.a is PIC. But my solution was declined in bugzilla and a different fix was opted for.
>
> Linking against shared phobos was just mentioned as immediate workaround.
>
> Changing over to -fPIC by default amd64 was one of multiple options that had to be carefully evaluated. It's fairly trivial to just demand a certain change without considering it's impact.

Not to mention that not all linux distributions work this way. Even not all the debian -> unbntu ones (such as Mint), and certainly not the ones based on red hat.

On Monday, 2 January 2017 at 13:51:15 UTC, Martin Nowak wrote: > On Sunday, 1 January 2017 at 23:55:37 UTC, deadalnix wrote: >> But it is not clear if anyone cares at this stage... > > It's fairly embarrassing to read so much uninformed noise. > > https://trello.com/c/E1LU0SAe/269-issue-16794-deb-not-working-on-ubuntu-16-10-because-of-default-pie-linking (added 5 days after bug report) > http://forum.dlang.org/post/o3ogr0$27hu$1@digitalmars.com > https://issues.dlang.org/show_bug.cgi?id=16794 Consider that if I'm misinformed, then nobody but you is. Welcome to the real world. Plus the fix was actually released yesterday, so it's not like I'm lagging by much. The internal meddling nonsense that's going on is none of any user business.

On Monday, 2 January 2017 at 13:52:29 UTC, Martin Nowak wrote: > On Monday, 2 January 2017 at 13:51:15 UTC, Martin Nowak wrote: >> On Sunday, 1 January 2017 at 23:55:37 UTC, deadalnix wrote: >>> But it is not clear if anyone cares at this stage... >> >> It's fairly embarrassing to read so much uninformed noise. > > Not to mention that everyone could have fixed this bug. Everyone could have written a patch, see it not being reviewed for a week, ping it on a daily basis, got asked for some changes, do the changes, wait another week, go hunt reviewers on IRC, finally got it merged, ask if that's possible to get it in the next release, get told that the patch was against master rather than stable or whatnot, get asked to go through the whole process all over again because why would anyone use git cherry pick, abandon, wait 6 month to get the fix live. Yes, that's how it goes.

On Monday, 2 January 2017 at 15:11:42 UTC, Basile B. wrote: > Not to mention that not all linux distributions work this way. Even not all the debian -> unbntu ones (such as Mint), and certainly not the ones based on red hat. The topic was fairly disputed for RH, but Jakub Jelinek is also the author of prelink, and seems a bit biased. There are also IRC logs available. https://pagure.io/fesco/issue/1113 It's true that ASLR is only a small security improvement that's not even relevant to many programs. I also ran several benchmarks and didn't found any measurable changes. So in the end going with PIC by default seemed OK.

Forums