Re: [Tuxmath-devel] Configuring the source code.

[blucalvin <blu...@gm...>]

Hello,

I have my git clone at :

{
haris@lorien:~/Desktop/tuxmath$ ls
ABOUT-NLS       buildw32        config.h.in   data        intl-patch
Makefile.in  options     tmlin.sh
acinclude.m4    ChangeLog       config.rpath  depcomp     linebreak
mingw        po          tuxmath.desktop
aclocal.m4      CMakeLists.txt  config.sub    doc         m4
missing      Portfile    tuxmath_preview.spec.in
AUTHORS         cmake-modules   configure     Info.plist  mac_cplibs.sh
NEWS         README      tuxmath.sh
autom4te.cache  config.guess    configure.ac  INSTALL     macosx
notesblurb   src         tuxmath.spec.in
build           config.h.cmake  COPYING       install-sh  Makefile.am
nsis         stamp-h.in
}

I did :

{
haris@lorien:~/Desktop/tuxmath$ autoreconf -vif || autoreconf -vi
autoreconf2.50: Entering directory `.'
autoreconf2.50: running: autopoint --force
autoreconf2.50: running: aclocal --force -I m4
autoreconf2.50: configure.ac: tracing
autoreconf2.50: configure.ac: not using Libtool
autoreconf2.50: running: /usr/bin/autoconf --force
configure.ac:117: error: possibly undefined macro: AC_CHECK_LIB
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
autoreconf2.50: /usr/bin/autoconf failed with exit status: 1
autoreconf2.50: Entering directory `.'
autoreconf2.50: running: autopoint
autoreconf2.50: running: aclocal -I m4
autoreconf2.50: configure.ac: tracing
autoreconf2.50: configure.ac: not using Libtool
autoreconf2.50: running: /usr/bin/autoconf
autoreconf2.50: running: /usr/bin/autoheader
autoreconf2.50: running: automake --add-missing --copy --no-force
autoreconf2.50: Leaving directory `.'
}

After doing the above, I followed Bruce's advice:

{
haris@lorien:~/Desktop/tuxmath$ mkdir build
haris@lorien:~/Desktop/tuxmath$ cd build
haris@lorien:~/Desktop/tuxmath/build$
}

How do I create a private built in this folder?
Should I run autoreconf in this temporary folder 'build'? If yes, what
should be the arguments to autoreconf?
Its a little confusing to me so as where and how to mention the path name.
After running the autoreconf, from where should I run the 'configure' file?

Thanks,
Haris.

PS: Do you have IRC?



On 24 August 2010 20:34, Brendan Luchen <bm...@ri...> wrote:

> Hi Haris et. al.
>
>
> >> What am I still not getting right?
> >
> > I'm at work on a windows box right now, so I can't test it, but I
> > think the problem with the above is an extra "-".  To pass the short
> > form of options to autoreconf, the single letter is prefixed by just
> > "-", e.g.:
> >
> > autoreconf -vi
> >
> > The long form of the options uses "--", e.g.:
> >
> > autoreconf --verbose --install
>
> Yup. "autoreconf -vif" is short for "autoreconf --verbose --install
> --force" whereas "autoreconf --vif" makes the program think you're
> trying to pass a single option called vif, which doesn't make any
> sense.
>
> I'm with Tim on this one. CMake is much nicer to use, especially for
> quick private builds such as yours.
>
> > Two other things:
> > 1. Until recently, there was a bug in configure.ac that caused
> > autoreconf to fail, with an error message "Unrecognized macro:
> > AC_CHECK_LIB", but if you just ran autoreconf a second time,
> > everything worked.  However that is fixed in the latest git sources.
>
> Awesome! What was the problem?
>
> --Brendan (who now, apparently, has autoconf on the brain)
>