On 01/02/2017 04:37 PM, Justin wrote:
> Hi all
>
> How about making USE=cuda a global USE?
>
> Description: Enable support for nVidia CUDA
I would say: "Enable support for NVIDIA CUDA", as that reflects how
NVIDIA now appears to refer to itself.
>
> Current Situation:
> [snip]
>
> More or le
> I have only tested this manually with run-parts, so I shall put it in
> cron.hourly right now and report back later.
MANPATH is definitely not set when executing cron scripts like that. I
deleted all mandoc.db files and waited for them to be regenerated. Only
the one in /usr/share/man was genera
> You shouldn't call those tools inside ebuild. If the build system is
> doing that, patch it out. In fact, I'm surprised sandbox doesn't catch
> this as an attempt to write outside allowed paths.
Okay, I shall remove any calls to database creation and just alert the
user.
> Are you sure this hap
On Wed, 4 Jan 2017 16:45:56 +
Wolfgang Mueller wrote:
> While working on an mdocml ebuild, I noticed that a call to `makewhatis'
> for mdocml or the corresponding `mandb' call for sys-apps/man-db does
> not create entries for gcc's or binutils' man pages. This is because
> the MANPATH environ
Hi,
While working on an mdocml ebuild, I noticed that a call to `makewhatis'
for mdocml or the corresponding `mandb' call for sys-apps/man-db does
not create entries for gcc's or binutils' man pages. This is because
the MANPATH environment is suppressed in ebuilds. I asked about this
in #gentoo-de
On 03/01/2017 15:24, Damien LEVAC wrote:
>
>
> On 01/03/2017 09:14 AM, Michael Mol wrote:
>> On Tuesday, January 3, 2017 12:05:10 PM EST Michał Górny wrote:
>>> On Tue, 3 Jan 2017 16:00:52 +0700 (+07)
>>>
>>> gro...@gentoo.org wrote:
On Mon, 2 Jan 2017, Brian Evans wrote:
> IMO, this o
On 01/04/2017 08:09 AM, Michael Palimaka wrote:
> On 04/01/17 12:57, Andrew Savchenko wrote:
>> Hi all,
>>
>> On Sun, 25 Dec 2016 22:55:27 +0300 Andrew Savchenko wrote:
>> [...]
>>> Another question: do we steel need to set STABLEREQ keyword for
>>> stabilization bugs? Since we now have a dedicated
On Mon, 2 Jan 2017 21:34:03 +
"Justin " wrote:
> Hi all
>
> How about making USE="c++11" a global USE?
>
> Description: Build using the C++11 standard.
>
> [...]
>
> Seems to be very consistent in usage.
...and yet a very bad idea.
As blueness pointed out, there's a major ABI incompatib
