Steven Chamberlain, on mer. 12 avril 2017 13:55:08 +0100, wrote:
> I expect there might be problems trying to build linux arches from a
> kfreebsd host. But we should try to find out, and then maybe fix it.
FWIW, I have been building hurd-i386 images from a linux box for a long
time without
Matthias Klose, le Mon 06 May 2013 16:22:30 +0200, a écrit :
- hurd never had openjdk support, and afaik, nobody is working on that.
There has been work towards this, notably by Jeremie Koenig. I don't
know the status, we just have not made it a strong priority so far.
Samuel
--
To
Kurt Roeckx, le Tue 26 Apr 2011 21:28:57 +0200, a écrit :
Is there a reason not to switch the remaining (release) arches
(ia64, kfreebsd-*, sparc, s390)? Maybe hurd-i386 too?
There's no real reason to defer hurd-i386, as it's basically like i386,
and the key packages (glibc/hurd/gnumach)
Steve Langasek, le Tue 16 Nov 2010 09:14:40 -0800, a écrit :
I don't argue that this makes --as-needed *correct* as a default, but I
think it's clear how using --as-needed may benefit a distribution in terms
of reducing churn when library dependencies change.
We agree on the second part, but
Florian Weimer, le Tue 16 Nov 2010 19:49:57 +0100, a écrit :
* Roland McGrath:
I can't see why you think --as-needed is fundamentally wrong or
unnecessary.
It is fundamentally wrong because -lfoo means I demand that the
initializers of libfoo.so run, whether or not I called anything
Matt Turner, le Mon 15 Nov 2010 19:51:10 -0500, a écrit :
On Mon, Nov 15, 2010 at 7:24 PM, Roger Leigh rle...@codelibre.net wrote:
What's the actual problem --as-needed is trying to solve?
The answer is mainly unwanted libraries being linked in as a result
of using pkg-config (and various
6 matches
Mail list logo
