This is the mail archive of the
automake@gnu.org
mailing list for the automake project.
Re: [sigc] building sigc++ with mips pro compiler
- To: Karl Nelson <kenelson@ece.ucdavis.edu>
- Subject: Re: [sigc] building sigc++ with mips pro compiler
- From: Charles Kerr <ckerr@osserver1.nssl.noaa.gov>
- Date: Tue, 22 Jun 1999 10:39:29 -0500
- Cc: Stephane Conversy <Stephane.Conversy@lri.fr>, libsigc@ece.ucdavis.edu, automake@gnu.org
- References: <376EC716.BBDCC9D3@lri.fr> <199906220645.XAA00405@teal.ece.ucdavis.edu>
On Mon, Jun 21, 1999 at 11:45:14PM -0700, Karl Nelson wrote:
> > Is it your responsability, or libtool, or automake
> > or anything else I don't know exactly the purpose ?
> This is a definite automake problem. (Thus it is going to be
> very hard to fix.) The file ${automake_prefix}/share/automake/depend2.am
> defines how to specify the options for the compiler dependency
> functions. However, this only really works for gnu and compilers
> that have very similar functionality. (Gtkmm list also has
> reports of similar problems with automake files on Sun compilers.)
> [snip]
>
> In the long term, this is a problem that GNU is going to have
> to deal with in some other way. The automake files produce what
> should be compiler independent Makefiles. [snip]
The automake people have been working on this issue recently.
This was in the automake mailing list last week:
> > "Currently, this [dependency] support requires the use of
> > GNU make and gcc." --Automake 1.4 Manual, top of page 8.
> > Any suggestions for adding more support?
>
> The automake CVS tree, branch user-dep-gen-branch, supports dependency
> tracking with any make and with most C compilers. There's a snapshot
> available in my home page.
Information on reaching the CVS tree can be found at
http://sourceware.cygnus.com/automake/.
I'm cc'ing the automake list to let them know that sigc++ and
Gtkmm clients are having problems related to this too.
Charles