Hi Tomislav, That should not be a problem, as you have already cleaned and regenerated files with all the autotools, not using any file generated on my computer(from automake, libtoolize, autoconf, ..)
As you already run the libtoolize and automake, you are not using those files from my computer: aclocal libtoolize --automake autoheader automake -a -c autoconf configure make make install Can you check what version of automake and libtoolize you have? Regards, Avin Patel Objective Systems, Inc. > -----Original Message----- > From: Tomislav Parčina [mailto:[EMAIL PROTECTED] > Sent: Wednesday, April 05, 2006 3:21 AM > To: Avin Patel; ooh323c > Subject: RE: [ooh323c-devel] ooh323 install problem > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf > > Of Avin Patel > > Sent: 4. travanj 2006 16:28 > > To: ooh323c > > Subject: RE: [ooh323c-devel] ooh323 install problem > > > > Hi Tomislav, > > This is the problem related to libtool version > > 1.5.8(new)/old(1.43). Please try to find the solution on > > libtool user group / faq. > > > > You will be able to find the reference to following on internet. > > > libtool: unrecognized option `--tag=CC' > > > Try `libtool --help' for more information. > > > > Let us know your findings. > > This is what Ralf have replied to me. > > <Ralph> > That is usually due to the package using an ancient Libtool > (before 1.5) and a non-ancient Automake (> 1.6) version. You > could ask the package maintainer to update both; current are > 1.5.22 and 1.9.6. > </Ralph> > > And this is how Brian has explained what Ralph has said. > > <Brian> > The versions of the tools on your system are irrelevent unless > you are the package's developer, i.e. you are the person that > created the source tarball. When just building somebody else's > source code you are using whatever version they used to create > the package. That is why Ralf said "due to the package using". > > The normal way that the autotools work is that the distributed > tarball is standalone, i.e. it includes copies of all generated > files so that the user doesn't even need > autoconf/automake/libtool installed on their system. This means > the developer of the package decides what versions are used, > which is normally a good thing. > > In your case you might need to regenerate everything, you can > normally do this with "autoreconf --install --force". Sometimes > though it is not that simple, and in those cases you need to run > a script that invokes the tools in the right order with the right > options, usually named something like "autogen.sh", "bootstrap.sh", etc. > > But what you really should do is report the failure to the > package's author so that he/she can address the version disparity > (if that indeed is the problem.) > </Brian> > > So, does ooh323 package includes copies of all generated files? > Do you need more information's from them? Do you need me anything to do? > > > -- > Tomislav Parcina > tparcina#lama.hr > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking > scripting language > that extends applications into web and mobile media. Attend the > live webcast > and join the prime developer group breaking into this new coding > territory! > http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642 > _______________________________________________ > ooh323c-devel mailing list > ooh323c-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/ooh323c-devel > > ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ ooh323c-devel mailing list ooh323c-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ooh323c-devel
