Getting failures trying to build glib from git

[Stephen Oberholtzer]

Jason,

Thank you! That got me on track and I was able to track down the issue.

In case anybody's interested, the offending commit was
e4ee3079c5afc3c1c3d2415f20c3e8605728f074.  Before that commit, the first
call to g_main_iteration would always complete immediately; Irssi was
unwittingly relying on that behavior.


On Mon, Mar 20, 2017 at 8:42 PM, Jason Crain <jason at inspiresomeone.us>
wrote:

> On Mon, Mar 20, 2017 at 06:38:55PM -0400, Stephen Oberholtzer wrote:
> > What do I need to do to be able to bisect the upstream code?
>
> Debian packages start from tarballs, not the git repo, so I'm not
> surprised that isn't working.  When I use 'git bisect' to track down a
> problem, I just use the git repo without including a debian directory
> with something like this:
>
> $ jhbuild shell # to set up environment variables and LD_LIBRARY_PATH
> $ ./autogen.sh --prefix=$HOME/jhbuild/install
> $ make && make install
>
> Then irssi should run against your local glib due to LD_LIBRARY_PATH.
>



-- 
-- Stevie-O
Real programmers use COPY CON PROGRAM.EXE
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20170321/c6a04d48/attachment-0001.html>