| I was looking back at the ChangeLog when I noticed this:
| 2000-05-23  Akim Demaille  <[EMAIL PROTECTED]>
| 
|         Simplify the interface: users shouldn't need to explicitly check
|         for special environments.
| 
|         * acspecific.m4 (AC_EXEEXT, AC_OBJEXT): AU defined to
|         nothing.  Replace them by...
|         (_AC_EXEEXT, _AC_OBJEXT): this.
| 
| Does this mean that I should not need to call AC_EXEEXT and AC_OBJEXT
| in my configure.in? Calling these two macros by default seems like
| a good idea.
| 
| Only problem is, when I remove them from my configure.in
| my Makefile.in seems to revert back to a non-portable state.
| (this file is generated by automake).
| 
| @@ -218,8 +216,8 @@
|  
|  maintainer-clean-compile:
|  
| -jikes$(EXEEXT): $(jikes_OBJECTS) $(jikes_DEPENDENCIES)
| -       @rm -f jikes$(EXEEXT)
| +jikes: $(jikes_OBJECTS) $(jikes_DEPENDENCIES)
| +       @rm -f jikes
|         $(CXXLINK) $(jikes_LDFLAGS) $(jikes_OBJECTS) $(jikes_LDADD) $(LIBS)
|  .cpp.o:
|         $(CXXCOMPILE) -c $<
| 
| 
| Is this a problem that needs to be fixed in automake or am
| I just missing something?

Arg, I never thought about this. Just don't remove them then.  I will
AU -> AC those guys so that people are not tempted to get rid of them.

Some solution is really needed to sync Autoconf and Automake.

        Akim

Reply via email to