On Mon, Nov 14, 2016 at 12:23:17AM +0200, Aaro Koskinen wrote:
> On Sat, Nov 12, 2016 at 09:02:37AM -0200, Thadeu Lima de Souza Cascardo wrote:
> > So, my proposal here is that we decide on a default page size for
> > buildds and kernels shipped with Debian, give the option for the
> > different
On Mon, Nov 14, 2016 at 09:17:56AM +0100, Mathieu Malaterre wrote:
> Hi,
>
> On Sat, Nov 12, 2016 at 12:02 PM, Thadeu Lima de Souza Cascardo
> wrote:
> > Hi,
> >
> > While recently investigating the mariadb bug, I found out the culprit is
> > in fact jemalloc. This library
Hi,
On Sat, Nov 12, 2016 at 12:02 PM, Thadeu Lima de Souza Cascardo
wrote:
> Hi,
>
> While recently investigating the mariadb bug, I found out the culprit is
> in fact jemalloc. This library assumes the system page size is the one
> that it found when building it. The
Hello Clint,
On 11/12/2016 01:39 PM, Clint Adams wrote:
> Hi Breno,
>
> It's unclear how to contact the ppc64el porters. Is there a mailing
> list?
Yes. We use the debian-powerpc mailing list. I am copying them to this email.
> Something appears to have broken with GHC's PPC64 code
Since the other day I get
N: Skipping acquire of configured file 'main/binary-powerpc/Packages' as
repository 'http://ftp.us.debian.org/debian stretch InRelease' doesn't
support architecture 'powerpc'
Is this just a temporary glitch or are we moving to debian-ports?
Regards
/M
On 11/15/2016 01:05 AM, Matti Palmström wrote:
> N: Skipping acquire of configured file 'main/binary-powerpc/Packages' as
> repository 'http://ftp.us.debian.org/debian stretch InRelease' doesn't support
> architecture 'powerpc'
>
> Is this just a temporary glitch or are we moving to
On Sat, Nov 12, 2016 at 10:00:53PM +0200, Adrian Bunk wrote:
> I do not understand this part.
>
> -maltivec should only be set for the code that is behind the runtime
> feature check, so this code is only run on hardware that has AltiVec.
Well a mistake in the configure script is making it set
7 matches
Mail list logo