Mark H Weaver writes:
> ng0 writes:
>
>> did we ever talk about that there's too little information on how to get
>> the current log file of a failed build? I need this right now (the full log)
>> and I can't remember how, and making use of the log folder in var/log/guix/
>> won't
>> help eithe
Hi,
here is my third part of the analysis:
Result
==
We can avoid all of the problems related to how Guix is using PYTHONPATH
quite simple. This will work for virtual environments, too.
Preliminary Proposal
===
To be able to install different minor versions of Pyth
ng0 writes:
>> > The flags I use (suggested by Debian Wiki[0]) are:
>> >
>> > CPPFLAGS=-D_FORTIFY_SOURCE=2
>>
>> How does this differ from "-O2 -D_FORTIFY_SOURCE" in CFLAGS?
>> I know O2 is optimization and that FORTIFY_SOURCE requires optimization
>> to be specified.
>
> Okay, I've read some
Ricardo Wurmus transcribed 486 bytes:
>
> ng0 writes:
>
> >> > The flags I use (suggested by Debian Wiki[0]) are:
> >> >
> >> > CPPFLAGS=-D_FORTIFY_SOURCE=2
> >>
> >> How does this differ from "-O2 -D_FORTIFY_SOURCE" in CFLAGS?
> >> I know O2 is optimization and that FORTIFY_SOURCE requires op
ng0 transcribed 1.6K bytes:
> Alex Vong transcribed 1.3K bytes:
> > Hello,
> >
> > n...@n0.is writes:
> >
> > > Hi,
> > >
> > > as we've long talked and not really taken action on hardening builds
> > > I've started working on an opt-in way as last discussed in
> > > september 2016, modifying the
On Sun, Mar 11, 2018 at 02:30:25PM +0100, Hartmut Goebel wrote:
> As I've been told, it's worse in Ruby, since rube is using the same
> gem-directories for all versions.
That is not accurate. Ruby uses even 'stable' numbers of minor
versions to split out. So 2.4.x and 2.6.x get installed in diff
Alex Vong transcribed 1.3K bytes:
> Hello,
>
> n...@n0.is writes:
>
> > Hi,
> >
> > as we've long talked and not really taken action on hardening builds
> > I've started working on an opt-in way as last discussed in
> > september 2016, modifying the gnu-build-system with a
> > #:hardening-flags k
On Sun, Mar 11, 2018 at 02:00:40PM +0100, Hartmut Goebel wrote:
> Am 10.03.2018 um 09:34 schrieb Pjotr Prins:
> > Generally, mixing Python2 and 3 in one profile makes no sense. During a
>
> I strongly disagree with the same arguments as Ricardo.
>
> The only reason we have problems installing bot
Am 11.03.2018 um 13:42 schrieb Pjotr Prins:
> But even in minor versions there are problems.
Yes, but it's not guix's job to solve the language programmer's problems.
Since quite some time, then python itnerpreters get installed as
"pythonX.Y", in addition to "pythonX" and "python". Thus it is pe
Am 10.03.2018 um 09:34 schrieb Pjotr Prins:
> Generally, mixing Python2 and 3 in one profile makes no sense. During a
I strongly disagree with the same arguments as Ricardo.
The only reason we have problems installing both python2 and python3 in
the same profile is: We are using PYTHONPATH in a w
On Sun, Mar 11, 2018 at 12:10:09PM +0100, Ricardo Wurmus wrote:
> Obviously, I strongly disagree :)
You should ;)
> On my CentOS and Fedora machines at work both versions are installed
> (with the system package manager) and nobody complains. I can conjure
> up a Python 2 environment by calling
Catonano writes:
> Look, there's a manual page about that !
>
> https://www.gnu.org/software/guix/manual/html_node/Debugging-Build-Failures.html#Debugging-Build-Failures
>
> Are we talking about the same thing ?
There is “guix build --log-file” (see the previous manual node).
--
Ricardo
Pjotr Prins writes:
> On Wed, Mar 07, 2018 at 08:50:48AM +0100, Ricardo Wurmus wrote:
>> Hi Guix,
>>
>> with the introduction of the collision avoidance feature that prevents
>> you from installing different variants of the same package into a
>> profile we made it impossible to install “python”
On 10/03/2018 09:34, Pjotr Prins wrote:
It still works with ad-hoc environments, but manifests containing both
Python versions cannot be instantiated any more. This is too strict,
because we know that these two variants don’t cause conflicts.
That is not my experience. Any mix is a problem.
Catonano transcribed 1.7K bytes:
> 2018-03-09 10:15 GMT+01:00 ng0 :
>
> > Hi,
> >
> > did we ever talk about that there's too little information on how to get
> > the current log file of a failed build? I need this right now (the full
> > log)
> > and I can't remember how, and making use of the lo
15 matches
Mail list logo