I wish I could help you...maybe one of the developers that knows our build
system better could help?
I'm running Fedora Core 9 and have the following SDL-related packages installed:
SDL-1.2.13-3.fc9.i386
SDL_gfx-devel-2.0.16-5.fc9.i386
SDL_gfx-2.0.16-5.fc9.i386
SDL_image-1.2.6-6.fc9.i386
SDL-dev
On Tue, 21 Dec 2004, Ray Cole wrote:
> Ugh. I give :-)
> I completely erase any sign of autoconf, automake, aclocal, and m4 from my
> system. I then installed the following from RedHat 9's distribution:
>
> autoconf-2.57-3.noarch.rpm
> automake-1.6.3-5.noarch.rpm
Well, automake
Got it. I ran aclocal, autoconf, and automake separately (without using
autoreconf) and ended up with a functioning setup. Odd...
Anyway, I ran ./configure, then make, and now have a new set of executables to
play with that appear to work :-)
-- Ray
Ray Cole wrote:
Ugh. I give :-)
I completely
Ugh. I give :-)
I completely erase any sign of autoconf, automake, aclocal, and m4 from my
system. I then installed the following from RedHat 9's distribution:
autoconf-2.57-3.noarch.rpm
automake-1.6.3-5.noarch.rpm
gtk+-devel-1.2.10-25.i386.rpm
gtk2-devel-2.2.1-4.i386.rpm
m4-1.4.1-11.i386.r
>Maybe someone else will have some suggestions other >than "install a newer
>system" ;)
Not me. It is eventually quicker and better to move to a recent distribution.
Just done it for exactly the same reasons Just upgrade, intalls are easy
enough (mind initio and SCSI and MDK 10.0 though.
Ma
On Thu, 16 Dec 2004, Ray Cole wrote:
> Well, I think I was in the wrong branch. I now re-fetched the code without
> specifying a branch. It looks like more modern stuff.
I haven't looked recently but there hasn't been any branch used in
a long time - always been the "HEAD"
Well, I think I was in the wrong branch. I now re-fetched the code without
specifying a branch. It looks like more modern stuff. Anyway, when I try to
run autogen.sh with it I get:
configure.ac:107: error: possibly undefined macro: AC_DEFINE
If this token and others are legitimate, please
I got past the autogen.sh stuff. Now I'm getting a plain ol' compiler error:
mpeg2encoptions.cc: In member function `int
MPEG2EncOptions::InferStreamDataParams(const MPEG2EncInVidParams&)':
mpeg2encoptions.cc:149: error: `mpeg_valid_framerate_code' undeclared (first
use this function)
mpeg2e
Glad to see someone else has the same type of problems :-) I'm using automake
1.8.5 and autoconf 2.59. I get a ton of AM_CONDITIONAL errors. I'd love to
try out some of the changes that have happened over the past year but can't
(sniff).
processing .
Running libtoolize...
You should add the c
On Tue, 14 Dec 2004, Ray Cole wrote:
> Glad to see someone else has the same type of problems :-) I'm using
> automake 1.8.5 and autoconf 2.59. I get a ton of AM_CONDITIONAL errors.
Are you sure that automake is completely installed and that you
have all of the -devel packa
Am Dienstag 14 Dezember 2004 18.33 schrieb Steven M. Schultz:
>
> On Tue, 14 Dec 2004, Michael Hanke wrote:
>
> > I tried to build the mjpegtools from CVS. Unfortunately, I could not run
> > autogen.sh successfully. The most important error:
> >
> > HAVE_PNG not defined in AM_CONDITIONAL
>
>
On Tue, 14 Dec 2004, Ray Cole wrote:
> I'd installed autoconf from source. I do have a /usr/local/share/aclocal-1.8
> directory. I tried creating a symbolic link from /usr/local/share/aclocal-1.8
> to /usr/share/aclocal but I get the exact same results :-(
But is anything _in_ that
Hi -
> On Wed, 15 Dec 2004, Michael Hanke wrote:
>
> > Did you do a fresh cvs checkout? If so then I do not know why
> > configure.in exists - it should be configure.ac now.
> That's it!
Super!
> I am running a weekly cron job for updating my CVS copy. It does not seem to
I'd installed autoconf from source. I do have a /usr/local/share/aclocal-1.8
directory. I tried creating a symbolic link from /usr/local/share/aclocal-1.8
to /usr/share/aclocal but I get the exact same results :-( I assume there is
some sort of conflict left behind by the fact I used to have
Am Mittwoch 15 Dezember 2004 08.33 schrieb Steven M. Schultz:
>
> On Wed, 15 Dec 2004, Michael Hanke wrote:
>
> > HAVE_PNG appears in configure.in. The stuff with HAVE_LIBPNG seems to be
ok.
> > The resulting configure script finds the png libraries...
>
> Then, for some reason, you do
On Wed, 15 Dec 2004, Michael Hanke wrote:
> HAVE_PNG appears in configure.in. The stuff with HAVE_LIBPNG seems to be ok.
> The resulting configure script finds the png libraries...
Then, for some reason, you do not have the current CVS version. There
is no such file as "config
Yep, I'm getting further. I'm now to the point where I am just missing some
.m4 files. I'll have to restore those. Will try again tomorrow or so.
Thanks for your help!
-- Ray
---
SF email is sponsored by - The IT Product Guide
Read honest & c
On Tue, 14 Dec 2004, Michael Hanke wrote:
> I tried to build the mjpegtools from CVS. Unfortunately, I could not run
> autogen.sh successfully. The most important error:
>
> HAVE_PNG not defined in AM_CONDITIONAL
That looks like an automake related message.
Hmmm, I see in conf
> I tried to build the mjpegtools from CVS.
> Unfortunately, I could not run
> autogen.sh successfully. The most important error:
>
> HAVE_PNG not defined in AM_CONDITIONAL
>
> What is going wrong? I have installed libpng-devel.
I, too, have a heck of a time building from CVS, and
I'm supposed
Hi,
I tried to build the mjpegtools from CVS. Unfortunately, I could not run
autogen.sh successfully. The most important error:
HAVE_PNG not defined in AM_CONDITIONAL
What is going wrong? I have installed libpng-devel.
Thank you.
Michael
-
20 matches
Mail list logo
