Re: Hwo to debug and teacking builds?

[ng0]

Actually you've sent this to the list and not off-list. So all is okay

I wouldn't know how to help with the emacs question.

I'm currently fixing lots of drupal to texinfo exports and after 70.000+
lines you just stop wanting a preview for every change.


Catonano transcribed 3.6K bytes:
> 2017-03-28 18:07 GMT+02:00 ng0 :
> 
> > Catonano transcribed 4.3K bytes:
> >
> >
> >
> > > Which is the source file ?
> >
> > doc/guix.texi
> >
> >
> Thank you.
> 
> I'd like to ask something about Emacs. A bit off topic but not that much.
> 
> I remember seeing an Emacs package that displays a preview of the whole
> document (buffer ?) in a small region of the window (frame ?)
> 
> So that you can know which portion of the document is currently displayed
> 
> Gedit, like many editors, does this, it's showed here (the small square on
> the right)
> ctrlv.in/938108
> 
> Too bad that I can't remember how it was called and I couldn't find
> anything related on line
> 
> If anyone has a hint, I'd appreciate that
> 
> It'd be helpful in browsing the guix.texi file that's quite large.
> 
> > How do I compile it ?
> >
> > I never got anything else than html to build with make of guix, (make
> > doc/guix.html)..
> >
> it's not super obvious. I know how texi2pdf etc works,
> > but this should at least be listed somewhere other than the Makefile.
> >
> 
> It definitely should be. I had no idea.
> And I wouldn't know what to look for in the Makefile
> 
> Thanks again

Re: Hwo to debug and teacking builds?

[ng0]

Catonano transcribed 4.3K bytes:
> 2017-03-28 11:52 GMT+02:00 Ludovic Courtès :
> 
> > Howdy!
> >
> > Hartmut Goebel  skribis:
> >
> > > when defining a new package, I often find myself spending *a lot* of
> > > time debugging and tweaking the build. E.g. the if the Makefile needs to
> > > be modified, or some test-cases adjusted.
> > >
> > > How do I "get into" the build container, so I can debug, modify files,
> > > rebuild and run tests there - in a closed environment (nearly) like the
> > > build-daemon has?
> >
> > Most of the time, you don’t need to get into a container.  In those
> > cases, it’s enough to do:
> >
> >   guix build -K foo
> >   # build fails…
> >   cd /tmp/guix-build-foo.drv-0
> >   source ./environment-variables
> >   cd foo-1.2
> >   …
> >
> > In some cases (for example when you have tests that fail in the build
> > environment but succeed once you’ve followed the steps above), you
> > really need a container similar to that created by guix-daemon.  In that
> > case, do:
> >
> >   guix build -K foo
> >   # build fails…
> >   cd /tmp/guix-build-foo.drv-0
> >   guix environment -C foo --ad-hoc strace gdb
> >   rm /bin/sh   # to be really like in the guix-daemon environment
> >   source ./environment-variables
> >   cd foo-1.2
> >   $GUIX_ENVIRONMENT/bin/strace -f -o log make check
> >   …
> >
> > That would probably make a good “Debugging Build Failures” section.
> >
> >
> >
> This is important information and it's more detailed than what Pjotr wrote
> in his wrap up
> 
> I'd do it myself but I don't know the first thing about the info system
> 
> Which is the source file ?

doc/guix.texi

> How do I compile it ?

I never got anything else than html to build with make of guix, (make
doc/guix.html).. it's not super obvious. I know how texi2pdf etc works,
but this should at least be listed somewhere other than the Makefile.

> Which Emacs mode should I use ?

Re: Hwo to debug and teacking builds?

[Ludovic Courtès]

Howdy!

Hartmut Goebel  skribis:

> when defining a new package, I often find myself spending *a lot* of
> time debugging and tweaking the build. E.g. the if the Makefile needs to
> be modified, or some test-cases adjusted.
>
> How do I "get into" the build container, so I can debug, modify files,
> rebuild and run tests there - in a closed environment (nearly) like the
> build-daemon has?

Most of the time, you don’t need to get into a container.  In those
cases, it’s enough to do:

  guix build -K foo
  # build fails…
  cd /tmp/guix-build-foo.drv-0
  source ./environment-variables
  cd foo-1.2
  …

In some cases (for example when you have tests that fail in the build
environment but succeed once you’ve followed the steps above), you
really need a container similar to that created by guix-daemon.  In that
case, do:

  guix build -K foo
  # build fails…
  cd /tmp/guix-build-foo.drv-0
  guix environment -C foo --ad-hoc strace gdb
  rm /bin/sh   # to be really like in the guix-daemon environment
  source ./environment-variables
  cd foo-1.2
  $GUIX_ENVIRONMENT/bin/strace -f -o log make check
  …

That would probably make a good “Debugging Build Failures” section.

Thoughts?

Ludo’.

Hwo to debug and teacking builds?

[Hartmut Goebel]

Hi,

when defining a new package, I often find myself spending *a lot* of
time debugging and tweaking the build. E.g. the if the Makefile needs to
be modified, or some test-cases adjusted.

How do I "get into" the build container, so I can debug, modify files,
rebuild and run tests there - in a closed environment (nearly) like the
build-daemon has?

-- 
Regards
Hartmut Goebel

| Hartmut Goebel  | h.goe...@crazy-compilers.com   |
| www.crazy-compilers.com | compilers which you thought are impossible |

Re: building Genshi

[Catonano]

2017-03-19 22:33 GMT+01:00 Catonano :

> Ludo,
>
> 2017-03-19 22:05 GMT+01:00 Ludovic Courtès :
>
>> Hi,
>>
>> Catonano  skribis:
>>
>> > genshi/_speedups.c: In function ‘escape’:
>> > genshi/_speedups.c:89:13: error: ‘PyUnicodeObject’ has no member named
>> ‘str’
>> >  inp = in->str;
>> >  ^
>>
>> I don’t know much about Python, but to me that suggests that Genshi
>> expects a different CPython version than the one it has here.  Maybe a
>> 2.x vs. 3.x issue?
>>
>
> I found it, it's here
> https://genshi.edgewall.org/ticket/555
>
> I didn't find it earlier :-/
>
> Thanks, anyway
>

O, naive question: say that I want to try to build genshi only for python2

How would I do that ?

Thanks