Man do I have a lot to catchup on. But as you requested, the lsusb is
rather large, I did grep around and think this puts me in the safe category;
idProduct 0x0004
iProduct5 RIM Composite Device
idProduct 0x
That looks to me like a 0004, but I am not the gur
On Fri, Apr 25, 2008 at 3:37 PM, Chris Frey <[EMAIL PROTECTED]> wrote:
> On Thu, Apr 24, 2008 at 10:30:30PM -0400, lance raymond wrote:
> > Seriously though, ignoring the barrybackup not syncing (error posted
> > before), how do you initiate the transfer/sync? The old treo worked via
> a
> > pilo
Hi All,
Just trying to compile the latest CVS and getting the following error,
any ideas where to start. here [1] is a link to the mailing list where
someone had this error before. No real solution,
checking whether the g++ linker (/usr/bin/ld) supports shared
libraries... yes
checking for g++
On Tue, Apr 29, 2008 at 03:46:05PM +1000, Jason Thomas wrote:
> Hi All,
>
> Just trying to compile the latest CVS and getting the following error,
> any ideas where to start. here [1] is a link to the mailing list where
> someone had this error before. No real solution,
Brian Edginton was the on
On Mon, Apr 28, 2008 at 01:05:48PM -0400, lance raymond wrote:
> Getting real close. I am getting an error on sync and have 1 question,
> so...
>
> The error is;
> msynctool --sync EvoBarry
> Synchronizing group "EvoBarry"
> Member 2 of type barry-sync had an error while connecting: (-1, error
>
I have tried both of those. I'm trying to build debian packages inside
a pbuilder chroot jail.
I've found a couple of build dependencies missing. perhaps there is
another that is causing this.
On Tue, 2008-04-29 at 02:00 -0400, Chris Frey wrote:
> On Tue, Apr 29, 2008 at 03:46:05PM +1000, Jason
On Tue, Apr 29, 2008 at 04:10:50PM +1000, Jason Thomas wrote:
> I have tried both of those. I'm trying to build debian packages inside
> a pbuilder chroot jail.
>
> I've found a couple of build dependencies missing. perhaps there is
> another that is causing this.
Ok, the next thing I'd check is
On Tue, Apr 29, 2008 at 02:22:25AM -0400, Chris Frey wrote:
> You may check the diff between your system's version and that, to see
> where it's going wrong. Check it before and after Debian's build process
> to make sure it hasn't changed.
Heh... that sounded like permission, which I didn't inte
