Where is ldc.gccbuiltins_x86?

Dicebot via digitalmars-d-ldc digitalmars-d-ldc at puremagic.com
Thu Jan 21 15:39:40 PST 2016

On Thursday, 21 January 2016 at 23:18:59 UTC, David Nadlinger 
> On 22 Jan 2016, at 0:07, Dicebot via digitalmars-d-ldc wrote:
>> Updated package with gccbuiltins_x86.di will propagate to 
>> mirrors soon.
> Thanks!
>> btw I wouldn't be able to use cmake install target even if I 
>> wanted (I always try to avoid that) because with current 
>> CMakeLists.txt it uses system path to bash-completion 
>> directory coming from `find_package` and not one inside prefix 
>> (unless I am missing another obscure cmake flag)
> You are of course free to package stuff in whatever way you 
> find the easiest. But can't you just use "make install 
> DESTDIR=…" like for pretty much every CMake or Autotools 
> project to get exactly what you want? Pretty sure that's 
> recommended in various Arch packaging guides too. If we install 
> files outside that directory, it's definitely a bug in our 
> CMake scripts.
>  — David

I tried using something akin to 
-DCMAKE_INSTALL_PREFIX=/path/to/pkg but it failed because of that 
mention bash-completion issue (tried to write to 

Off-Topic Philosophy:

In general it is sort of my personal obsession that goes against 
usual approach :) I started to do it for two reasons:

1) it forces to learn something about internal project path/file 
organization (which fits my understanding of packager 
2) it encourages to actually improve the layout to make it more 
fitting for specific distro and provide some useful additions 
(i.e. systemd service files)

Sometimes it results in "oops" moments like this one but I 
believe overall user experience gets improved a lot. Of course 
this approach is only viable if one maintains relatively small 
amount of packages.

More information about the digitalmars-d-ldc mailing list