Am Mittwoch 04 März 2009 14:05:34 schrieb Marc Rios Valles:
> Hi,
>
> I've been playing around the new opensc-0.11.7 and I think is not
> correct to add the m4 referents to libtool because it makes to fail the
> compilation in some systems. I am refering to m4/libtool.m4 and
> m4/lt*.m4 files. These files differs in one system to another and are
> putted by aclocal so are not needed. In Fedora 10 for example when you
> try to compile you get:

did you only run configure, or did you run some extra commands like
aclocal, bootstrap, autoheader, automake or anything like that?

did you enable maintainer mode in configure?

the package process has the usual goal to allow any user to compile
opensc without needing any of those packages. so you should only
need the pkg-config tool, the packages we depend on, make and gcc
(and friends like ld, asm, etc.).

libtool is added by the package process to the source, and the m4/libtool.m4
and related files are there so autoconf knows about that. (no, I'm
no expert here, but they contain the makros so autoconf knows
how to use ./libtool I guess).

my point of view is:
* bug fixing should be possible with editing *.c only
  (yes, that doesn't work if you want to add new *.c files)
* developers should build from svn source or from "make maintainer-clean",
  have all those tools installed installed and run ./bootstrap
* people compiling opensc should not need autoconf/make/libtool/... at all
  (except for libltdl with development files and the other libraries),
  and should run ./configure only (without enabling maintainer mode)
  and that should work.

which case fits your description best, and what did you exactly / what are you
trying to do?

I know that some distributions do strange things with autoconf based software,
such as replacing files, re-running autoconf and so on. I'm no expert here,
no idea why that is done, but if they modify the source, I hope they know what
they are doing.

Regards, Andreas
_______________________________________________
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Reply via email to