Oops ... sorry Scott, didn't realise I wasn't replying to list before :(
Hi Guys
Thanks for the replies. Just to confirm, I am building an entirely upstart
dependantdistro (so no initial references to old init or /etc/init.d stuff), so
should I be linkingstatically or dynamically? ( I am leading toward the latter)
CheersGrail
> Subject: Re: Compile from srource
> From: [email protected]
> To: [email protected]
> CC: [email protected]; [email protected]
> Date: Mon, 1 Mar 2010 15:56:21 +0000
>
> On Mon, 2010-03-01 at 16:45 +0100, Michael Biebl wrote:
>
> > 2010/3/1 Scott James Remnant <[email protected]>:
> > >
> > > bzr branch lp:upstart
> > > cd upstart
> > > autoreconf -i
> > > ./configure --with-local-libnih=../libnih
> > > make
> >
> > This will link upstart dynamically against libnih though, i.e. you
> > will also need to install libnih to /lib
> This is intended for when you're not actually installing, you can run
> init out of Upstart's source tree and it'll be linked to the
> non-installed libnih
>
> But yes, this will link to libnih as a dynamic library, so should you
> run "make install" you'll have to do the same in the other.
>
> You can link statically with just:
>
> ./configure --with-local-libnih=../libnih --disable-shared
>
> > So it does not quite behave as the old nihify script.
> >
> It's not intended to.
>
> Scott
> --
> Have you ever, ever felt like this?
> Had strange things happen? Are you going round the twist?
_________________________________________________________________
View photos of singles in your area! Browse profiles for FREE
http://clk.atdmt.com/NMN/go/150855801/direct/01/--
upstart-devel mailing list
[email protected]
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/upstart-devel