> On 29 March 2017 at 19:58 Dan Williams wrote:
>
> On Wed, 2017-03-29 at 16:52 +0100, Colin Helliwell wrote:
>
> > > On 29 March 2017 at 15:13 Dan Williams wrote:
> > >
> > > On Wed, 2017-03-29 at 14:32 +0100, Colin Helliwell wrote:
> > >
> > > > > > On 27 March 2017 at 14:25 Colin Helliwel
On Wed, 2017-03-29 at 16:52 +0100, Colin Helliwell wrote:
> > On 29 March 2017 at 15:13 Dan Williams wrote:
> >
> > On Wed, 2017-03-29 at 14:32 +0100, Colin Helliwell wrote:
> >
> > > > > On 27 March 2017 at 14:25 Colin Helliwell > > > > -sys tems.com> wrote:
> > >
> > > ...
> > >
> > > > > .
> On 29 March 2017 at 15:13 Dan Williams wrote:
>
> On Wed, 2017-03-29 at 14:32 +0100, Colin Helliwell wrote:
>
> > > > On 27 March 2017 at 14:25 Colin Helliwell > > > tems.com> wrote:
> >
> > ...
> >
> > > > ... but still have subsequent errors which seem to have been due
> > > > to output
On Wed, 2017-03-29 at 14:32 +0100, Colin Helliwell wrote:
> > > On 27 March 2017 at 14:25 Colin Helliwell > > tems.com> wrote:
> > >
>
> ...
> > > ... but still have subsequent errors which seem to have been due
> > > to output directories not having been created e.g. libnm-core,
> > > introspec
> > On 27 March 2017 at 14:25 Colin Helliwell
> > wrote:
> >
...
> > ... but still have subsequent errors which seem to have been due to output
> > directories not having been created e.g. libnm-core, introspection.
> > I can get it to limp a little further by creating the directories in the
>
> On 27 March 2017 at 17:04 Dan Williams wrote:
>
...
>
> The build process takes Introspection data from the NM objects
> (NMDevice, NMConnection, etc) and generates files that nmcli uses to
> provide help text, properties, etc, rather than hardcoding things
> twice. So unfortunately, if you w
On Tue, 2017-03-28 at 07:21 +0100, Colin Helliwell wrote:
> > On 27 March 2017 at 17:04 Dan Williams wrote:
> >
>
> ...
> >
> > The build process takes Introspection data from the NM objects
> > (NMDevice, NMConnection, etc) and generates files that nmcli uses
> > to
> > provide help text, prop
> On 27 March 2017 at 17:04 Dan Williams wrote:
>
...
>
> The build process takes Introspection data from the NM objects
> (NMDevice, NMConnection, etc) and generates files that nmcli uses to
> provide help text, properties, etc, rather than hardcoding things
> twice. So unfortunately, if you w
On Mon, 2017-03-27 at 16:12 +0100, Colin Helliwell wrote:
> > On 27 March 2017 at 14:25 Colin Helliwell > ms.com> wrote:
> >
> > I think it was missing [under yocto/bitbake] the autogen.sh step.
> > I've corrected that (as a 'pre-configure' step), but still have
> > subsequent errors which seem t
> On 27 March 2017 at 14:25 Colin Helliwell
> wrote:
>
> I think it was missing [under yocto/bitbake] the autogen.sh step.
> I've corrected that (as a 'pre-configure' step), but still have subsequent
> errors which seem to have been due to output directories not having been
> created e.g. lib
I think it was missing [under yocto/bitbake] the autogen.sh step.
I've corrected that (as a 'pre-configure' step), but still have subsequent
errors which seem to have been due to output directories not having been
created e.g. libnm-core, introspection.
I can get it to limp a little further by cr
On Fri, 2017-03-24 at 16:07 +, colin.helliw...@ln-systems.com
wrote:
> Just trying to migrate my build from 1.4.2 (from a tarball) to 1.6
> (from
> git), but getting some errors in the configure.
> I am passing some additional configure options, but this seems to be
> something more basic?
Def
Just trying to migrate my build from 1.4.2 (from a tarball) to 1.6 (from
git), but getting some errors in the configure.
I am passing some additional configure options, but this seems to be
something more basic?
$ ls
tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/networkmanager/1.6-r0/git/bu
ild-
13 matches
Mail list logo
