Build failing on OS X

[dalboy]

I am trying to install xuggler onto OS X 10.5.6 but it is failing to
build. It can't seem to compile the libmp3lame project. I have the
latest xcode installed and am pretty sure I meet all the minimum
requirements.

You can see the output here http://pastie.org/410828

Any ideas what I am missing?

Dallas

[Art Clarke]

Looks like either you have an old version of XCode, or GCC.  You're not even building libmp3lame.  Try upgrading both of those.

- Art

--
http://www.xuggle.com/
xu‧ggle (zŭ' gl) v. To freely encode, decode, and experience audio and video.

Use Xuggle to get the power of FFMPEG in Java.

[dalboy]

I checked the versions of xcode and gcc. I have installed the latest
version of Xcode (3.2.1). And the gcc version is 4.0.1

development:src developer$ gcc -version
i686-apple-darwin9-gcc-4.0.1: no input files

and gcc is on the path

development:src developer$ which gcc
/usr/bin/gcc

I had a look in the config.log for libmp3lame ( /usr/local/src/xuggle-
xuggler/build/native/i386-apple-darwin9.6.0/captive/libmp3lame/csrc/
config.log ) which you can see here http://pastie.org/411596.

and it looks like the reason the build is failing is on line 112

/usr/local/src/xuggle-xuggler/build/native/i386-apple-
darwin9.6.0/../../../captive/libmp3lame/csrc/configure: line 3129: ./
a.out: Bad CPU type in executable

I am trying to install this on an intel macbook. any ideas why I would
be getting "Bad CPU type in executable"?

Thanks

Dallas

On Mar 9, 12:31 am, Art Clarke <acla...@xuggle.com> wrote:
> Looks like either you have an old version of XCode, or GCC.  You're not even
> building libmp3lame.  Try upgrading both of those.
>
> - Art
>

> On Sun, Mar 8, 2009 at 5:18 AM, dalboy <dallastay...@gmail.com> wrote:
>
> > I am trying to install xuggler onto OS X 10.5.6 but it is failing to
> > build.  It can't seem to compile the libmp3lame project.  I have the
> > latest xcode installed and am pretty sure I meet all the minimum
> > requirements.
>

> > You can see the output herehttp://pastie.org/410828

>
> > Any ideas what I am missing?
>
> > Dallas
>

> --http://www.xuggle.com/

[Art Clarke]

I think you meant Xcode 3.1.2, but otherwise we have the same versions and it works here.  I saw a reference online to people getting that error with Apples, and it having something to do with PowerPC based, or non-core-duo based intel macs.

Try seeing if you can do a 32-bit build by doing:

ant clobber
ant -Dbuild.m64=no run-tests

If that works, then Xuggler should run under Java 1.5 (but not 1.6).  Let me know, and if that's the problem, we'll try to figure out a fix.

- Art

--

[dalboy]

oops, yes I meant XCode 3.1.2. I thought I had a pretty standard
setup so was surprised it wasn't working. The info on my macbook from
system profiler is

Model Name: MacBook
Model Identifier: MacBook1,1
Processor Name: Intel Core Duo
Processor Speed: 2 GHz
Number Of Processors: 1
Total Number Of Cores: 2

I only have java 1.5 installed and haven't updated to 1.6.

development:~ developer$ java -version
java version "1.5.0_16"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_16-
b06-284)
Java HotSpot(TM) Client VM (build 1.5.0_16-133, mixed mode, sharing)


Forcing it to build as 32 bit with -Dbuild.m64=no solved the problem
and I was able to build and run the tests successfully.

Does this all make sense? Is there any other info that would be
helpful?

Thanks for your help Art.

Dallas

On Mar 9, 5:49 pm, Art Clarke <acla...@xuggle.com> wrote:
> I think you meant Xcode 3.1.2, but otherwise we have the same versions and
> it works here.  I saw a reference online to people getting that error with
> Apples, and it having something to do with PowerPC based, or non-core-duo
> based intel macs.
>
> Try seeing if you can do a 32-bit build by doing:
>
> ant clobber
> ant -Dbuild.m64=no run-tests
>
> If that works, then Xuggler should run under Java 1.5 (but not 1.6).  Let me
> know, and if that's the problem, we'll try to figure out a fix.
>
> - Art
>
>
>
>
>
> On Mon, Mar 9, 2009 at 5:50 AM, dalboy <dallastay...@gmail.com> wrote:
>
> > I checked the versions of xcode and gcc. I have installed the latest
> > version of Xcode (3.2.1).  And the gcc version is 4.0.1
>
> > development:src developer$ gcc -version
> > i686-apple-darwin9-gcc-4.0.1: no input files
>
> > and gcc is on the path
>
> > development:src developer$ which gcc
> > /usr/bin/gcc
>
> > I had a look in the config.log for libmp3lame ( /usr/local/src/xuggle-
> > xuggler/build/native/i386-apple-darwin9.6.0/captive/libmp3lame/csrc/

> > config.log )  which you can see herehttp://pastie.org/411596.

[Art Clarke]

Hmm... that is odd.  That's the exact same setup we have here.  The only difference is we use Java 1.6 and do a 64-bit GCC build.  I'm wondering if something got installed with Java 1.6 (which is only 64-bit on Mac's) or with XCode that is necessary for doing x86_64 binary builds?

For now though, sounds like you worked around it.  We'll keep our eye open for this in the future (although the doc pages should already mention the need to build 32-bit if you're running java 1.5 on Macs).

Also, any volunteers to build mac installers would be most graciously welcomed :)

- Art

--