> as i mentioned before, unless there's an actual issue, i'm a big fan
> of pushing version upgrades so that any problems can be identified
> sooner rather than later. if a newer version of some toolchain
> component works on all but one architecture, i think it's more useful
> to bump the de
On Fri, 28 Mar 2008, Michael wrote:
>
> I am getting an automake version mismatch when compiling libsamplerate.
>
> This worked for me:
>
> define Build/Compile
> pushd $(PKG_BUILD_DIR) && aclocal && automake && popd
> .
>
> I can make that an official patch if you would like.
app
On Fri, 28 Mar 2008 04:49:49 pm Robert P. J. Day wrote:
> On Fri, 28 Mar 2008, Michael wrote:
> > I am getting an automake version mismatch when compiling libsamplerate.
> >
> > This worked for me:
> >
> > define Build/Compile
> > pushd $(PKG_BUILD_DIR) && aclocal && automake && popd
> > ..
On Thu, 27 Mar 2008, Imre Kaloz wrote:
> On 2008.03.27. 23:37:47 Luigi 'Comio' Mantellini <[EMAIL PROTECTED]> wrote:
>
>
>
> > Ok. Anyway the compiler gcc4.3 supports a lot new cpus (like the
> > coldfire) :) opening new development horizons.
> >
>
> Sure, as AVR32 uses gcc 4.2.3.. Some targets w
On Fri, 28 Mar 2008, Michael wrote:
>
> I am getting an automake version mismatch when compiling libsamplerate.
>
> This worked for me:
>
> define Build/Compile
> pushd $(PKG_BUILD_DIR) && aclocal && automake && popd
> .
>
> I can make that an official patch if you would like.
the
On Thu, 27 Mar 2008, Imre Kaloz wrote:
> On 2008.03.27. 23:03:59 Robert P. J. Day <[EMAIL PROTECTED]> wrote:
>
> >
> > is there any inherent difficulty in bumping up the software versions
> > of the toolchain components? say, binutils to 2.18 and gcc to 4.2.3?
> > i realize you can always do th
