Walter Bright wrote:
Spacen Jasset wrote:
For us Linux DMD users a bug should be raised against dmd so that
Walter will hopefully compile against an older glibc on future releases.
Yet when I do that the other half of the linux users have a problem.
Do you know what problems they had Walter,
Steven Schveighoffer wrote:
"Spacen Jasset" wrote
Steven Schveighoffer wrote:
...chop
For us Linux DMD users a bug should be raised against dmd so that Walter
will hopefully compile against an older glibc on future releases.
As long as it doesn't cause weird problems. I have had weird stu
Spacen Jasset wrote:
For us Linux DMD users a bug should be raised against dmd so that Walter
will hopefully compile against an older glibc on future releases.
Yet when I do that the other half of the linux users have a problem.
"Spacen Jasset" wrote
> Steven Schveighoffer wrote:
>> "Spacen Jasset" wrote
>>> Steven Schveighoffer wrote:
You may have to statically link (which, of course, is not officially
supported by glibc, for very stupid reasons).
>>> I am not sure that the reasons are "stupid". It is similar,
Steven Schveighoffer wrote:
"Spacen Jasset" wrote
Steven Schveighoffer wrote:
You may have to statically link (which, of course, is not officially
supported by glibc, for very stupid reasons).
I am not sure that the reasons are "stupid". It is similar, for example to
kernel32.dll on windows, w
"Spacen Jasset" wrote
> Steven Schveighoffer wrote:
>> You may have to statically link (which, of course, is not officially
>> supported by glibc, for very stupid reasons).
>
> I am not sure that the reasons are "stupid". It is similar, for example to
> kernel32.dll on windows, which you cannot l
Steven Schveighoffer wrote:
"dsimcha" wrote
Apparently, DMD for Linux requires a non-ancient version of Glibc to work,
and
worse yet, all the stuff compiled by it requires a similarly non-ancient
version. The problem is that I'm trying to run some jobs on a cluster
that
has an ancient versio
"dsimcha" wrote
> Apparently, DMD for Linux requires a non-ancient version of Glibc to work,
> and
> worse yet, all the stuff compiled by it requires a similarly non-ancient
> version. The problem is that I'm trying to run some jobs on a cluster
> that
> has an ancient version of Linux that my s
dsimcha wrote:
Apparently, DMD for Linux requires a non-ancient version of Glibc to work, and
worse yet, all the stuff compiled by it requires a similarly non-ancient
version. The problem is that I'm trying to run some jobs on a cluster that
has an ancient version of Linux that my sysadmin doesn
dsimcha wrote:
Apparently, DMD for Linux requires a non-ancient version of Glibc to work, and
worse yet, all the stuff compiled by it requires a similarly non-ancient
version. The problem is that I'm trying to run some jobs on a cluster that
has an ancient version of Linux that my sysadmin doesn
== Quote from Andrei Alexandrescu (seewebsiteforem...@erdani.org)'s article
> dsimcha wrote:
> > Apparently, DMD for Linux requires a non-ancient version of Glibc to work,
> > and
> > worse yet, all the stuff compiled by it requires a similarly non-ancient
> > version. The problem is that I'm try
dsimcha wrote:
Apparently, DMD for Linux requires a non-ancient version of Glibc to work, and
worse yet, all the stuff compiled by it requires a similarly non-ancient
version. The problem is that I'm trying to run some jobs on a cluster that
has an ancient version of Linux that my sysadmin doesn
Apparently, DMD for Linux requires a non-ancient version of Glibc to work, and
worse yet, all the stuff compiled by it requires a similarly non-ancient
version. The problem is that I'm trying to run some jobs on a cluster that
has an ancient version of Linux that my sysadmin doesn't want to upgrad
13 matches
Mail list logo
