Problem solved :)
Sent using BlackBerry® from Orange
-Original Message-
From: Chris Frey
Date: Fri, 21 Jan 2011 14:29:00
To: Barry project development discussion
Reply-To: Barry project development discussion
Subject: Re: [Barry-devel] Opensync-plugin and GUI build failure.
In
With all due respect I packaged Barry for Salix 13.1 as well as many personal
builds, it is only now I have encountered a problem. I'm also building this for
-current (since the release of Salix 13.2alpha1) and the updates in git solve a
number of issues.
The problem is solved by exporting the P
This issues seams to be resolved, at least for my 9700, in git (cloned today).
-Phill
Sent using BlackBerry® from Orange
--
Gaining the trust of online customers is vital for the success of any company
that requires sensit
The lines echo fine but the variables aren't exported.
I'll try to remember to upload a build log and diff for you later.
-Phill
Sent using BlackBerry® from Orange
-Original Message-
From: Chris Frey
Date: Fri, 7 Jan 2011 15:06:53
To: Barry project development discussion
Reply-To: Bar
I'm packaging barry for Salix which is basically an extension (not really a
fork) of Slackware so autoconf, automake, pkg-config, and libtool are from
Slackware. I've tried building this checkout against 13.1 and -current with the
same outcome.
I agree, it's strange. I can't see why it doesn't
Exporting the PKG_CONFIG_PATH (same as line 20064 in the configure script)
before running configure seams to have solved the problem.
Thanks.
Sent using BlackBerry® from Orange
-Original Message-
From: Chris Frey
Date: Thu, 6 Jan 2011 20:10:52
To:
Reply-To: Barry project development
The opensync-plugin and gui fail to compile from a current git checkout using
--enable-gui and --enable-opensync-plugin.
The errors I receive are due to missing libraries, libbarry0 and libbarrysync0.
If I build opensync-plugin and gui as separate packages after installing
everything else they
