Re: Gigabeat S unstable

Barry Wardell wrote: On Fri, Oct 30, 2009 at 8:54 PM, Rafaël Carré > wrote: libtool removes -arch for some reason, typing the g++ command line with -arch ppc should work OK, after lots of manual adding of -arch ppc to g++ lines, I finally got libusb to c

Re: Gigabeat S unstable

On Fri, Oct 30, 2009 at 8:54 PM, Rafaël Carré wrote: > libtool removes -arch for some reason, typing the g++ command line with > -arch ppc should work > OK, after lots of manual adding of -arch ppc to g++ lines, I finally got libusb to cross-compile for ppc. I now have a disk image with a univers

Re: Gigabeat S unstable

Barry Wardell wrote: Rob has confirmed that this works for him. Now, we just need someone to build a ppc version. I would do it, but haven't been able to figure out how to cross-compile libusb and libmtp for ppc. Great, thanks very much! So now we just need the release version (built with

Re: Gigabeat S unstable

On Fri, 30 Oct 2009 20:32:30 +0100 Barry Wardell wrote: > On Fri, Oct 30, 2009 at 5:51 PM, Rafaël Carré > wrote: > > > open$unix_2003 or something like that? > > > > These were the kind of errors that were affecting the compile of > beastpatcher and were fixed by splitting the compiling and lin

Re: Gigabeat S unstable

On Fri, Oct 30, 2009 at 5:51 PM, Rafaël Carré wrote: > open$unix_2003 or something like that? > These were the kind of errors that were affecting the compile of beastpatcher and were fixed by splitting the compiling and linking into two steps. The specific error, I get when compiling libusb with

Re: Gigabeat S unstable

On Fri, 30 Oct 2009 15:15:10 +0100 Barry Wardell wrote: > On Fri, Oct 30, 2009 at 3:03 PM, Rafaël Carré > wrote: > > > just add -arch ppc to CFLAGS and LDFLAGS : > > > > CFLAGS="-arch ppc" LDFLAGS="-arch ppc" ./configure --xxx > > > > Unfortunately, that doesn't work with libusb. It fails comp

Re: Gigabeat S unstable

On Fri, Oct 30, 2009 at 3:03 PM, Rafaël Carré wrote: > just add -arch ppc to CFLAGS and LDFLAGS : > > CFLAGS="-arch ppc" LDFLAGS="-arch ppc" ./configure --xxx > Unfortunately, that doesn't work with libusb. It fails complaining of undefined symbols when I run make.

Re: Gigabeat S unstable

On Fri, 30 Oct 2009 14:54:51 +0100 Barry Wardell wrote: > On Fri, Oct 30, 2009 at 3:03 AM, Robert Menes > wrote: > > > Barry Wardell wrote: > > > If anyone wants, I can send them my compiled version of > > > beastpatcher for OSX Intel. > > > > > > > I'm interested! Send along! :) > > > Rob has

Re: Gigabeat S unstable

On Fri, Oct 30, 2009 at 3:03 AM, Robert Menes wrote: > Barry Wardell wrote: > > If anyone wants, I can send them my compiled version of beastpatcher for > > OSX Intel. > > > > I'm interested! Send along! :) Rob has confirmed that this works for him. Now, we just need someone to build a ppc versi

Re: Gigabeat S unstable

Barry Wardell wrote: > If anyone wants, I can send them my compiled version of beastpatcher for > OSX Intel. > I'm interested! Send along! :) --Rob -- Nobody's ever lost in life...they're merely taking the scenic route. == Please avoid sending me Word or PowerPoint a

Re: Gigabeat S unstable

I don't have a Gigabeat S to test it on, but I did manage to compile beastpatcher on OSX using the attached patch. This assumes that there is in the gigabeast directory a libusb.a and usb.h file from libusb-0.1.12 and also libmtp.a and libmtp.h from libmtp-1.0.1. If anyone wants, I can send them m

Re: Gigabeat S unstable

Alex Parker wrote: > > It doesn't build, I (personally) have no idea why. If someone could get > it to, I'm sure we could find a tester. > On Mac OS X, libmtp.a and libusb.a are installed to /usr/local/lib/ (at least on my Mac, anyway), so we need to point to that location in order to build on

Re: Gigabeat S unstable

Alex Parker wrote: > > It doesn't build, I (personally) have no idea why. If someone could get > it to, I'm sure we could find a tester. > Since I'm one of the few devs/staff with OS X, I'll see if I can get libusb and libmtp to build and install so I can get beastpatcher to build. --Rob -- N

Re: Gigabeat S unstable

Alex Parker wrote: Hi All, I'd like to have the beast as unstable - it has a released bootloader and released beastpatcher versions for linux (32 and 64 bit) and windows, and the manual contains manual install instructions. Only mac is missing, owing to a lack of developers on that platform. P

Re: Gigabeat S unstable

Rafaël Carré wrote: On Thu, 29 Oct 2009 23:46:50 +0100 Alex Parker wrote: Hi All, I'd like to have the beast as unstable - it has a released bootloader and released beastpatcher versions for linux (32 and 64 bit) and windows, and the manual contains manual install instructions. Only mac is m

Re: Gigabeat S unstable

Rafaël Carré wrote: What is missing for building beastpatcher for mac? does it have special dependancies? I could build a binary but can't test myself. It doesn't build, I (personally) have no idea why. If someone could get it to, I'm sure we could find a tester. Alex

Re: Gigabeat S unstable

Hilton Shumway wrote: What all is needed to get beastpatcher to work on OS X? Does it just need to be compiled? No, if it were that simple it would have been done :) Alex

Re: Gigabeat S unstable

On Thu, 29 Oct 2009 23:46:50 +0100 Alex Parker wrote: > Hi All, > > I'd like to have the beast as unstable - it has a released bootloader > and released beastpatcher versions for linux (32 and 64 bit) and > windows, and the manual contains manual install instructions. Only > mac is missing, owi

Re: Gigabeat S unstable

On Thu, Oct 29, 2009 at 4:46 PM, Alex Parker wrote: > Hi All, > > I'd like to have the beast as unstable - it has a released bootloader > and released beastpatcher versions for linux (32 and 64 bit) and > windows, and the manual contains manual install instructions.  Only mac > is missing, owing t

Gigabeat S unstable

Hi All, I'd like to have the beast as unstable - it has a released bootloader and released beastpatcher versions for linux (32 and 64 bit) and windows, and the manual contains manual install instructions. Only mac is missing, owing to a lack of developers on that platform. Personally I don't th