On Wed, 2018-01-17 at 16:07 +, John Emmas wrote:
> On 17/01/2018 11:04, John Emmas wrote:
> >
> > I'll look a bit further into this and see if I can figure out
> > what's
> > gone wrong.
> >
>
> This turned out to be a problem with TortoiseGit. Some of glib's
> python
> files contain
On 17/01/2018 11:04, John Emmas wrote:
I'll look a bit further into this and see if I can figure out what's
gone wrong.
This turned out to be a problem with TortoiseGit. Some of glib's python
files contain lines looking like this:-
from .whatever import something
For some
On 17/01/2018 10:38, Philip Withnall wrote:
What’s the output of `git status`?
For both 'codegen_main.py' and 'codegen_docbook.py' I see this output:-
# On branch master
# Your branch is ahead of 'upstream/master' by 260 commits.
#
nothing to commit (working directory clean)
(I think
On Wed, 2018-01-17 at 10:26 +, John Emmas wrote:
> On 17/01/2018 09:51, Philip Withnall wrote:
> > Exactly what commit are you building?
> >
> > > [...]
> > >
> >
> > That’s not what the code currently looks like:
> >
>
> Thanks for the quick response Philip. The latest commit here
On 17/01/2018 09:51, Philip Withnall wrote:
Exactly what commit are you building?
[...]
That’s not what the code currently looks like:
Thanks for the quick response Philip. The latest commit here is
#5fba62ade by Benjamin Berg on 15 Jan 2018 (gmessages: Flush output
stream after
On Wed, 2018-01-17 at 09:44 +, John Emmas wrote:
> I'm not yet building with meson so forgive me if this is just down to
> my
> build system being out-of-date !!
>
> The problem happens when I try to build glib/gio from yesterday's
> git
> master.
Exactly what commit are you building?
>
I'm not yet building with meson so forgive me if this is just down to my
build system being out-of-date !!
The problem happens when I try to build glib/gio from yesterday's git
master. More specifically it happens when building the 'gdbus-codegen'
stuff. 'The file
