Re: Bug in installation

Re: Bug in installation

[Jeffrey A Law]

  In message <9712052020.AA29379@kona.>you write:
  > >>>>> "Jeffrey" == Jeffrey A Law <law@cygnus.com> writes:
  > 
  >  Jeffrey> Or maybe we stop installing f2c outside of $(libsubdir) and
  >  Jeffrey> instead have configure issue a warning about the existance
  >  Jeffrey> of an old f2c in /usr/include or /usr/local/include?
  > 
  > Sounds like a great idea.  Hardwired destinations are a pain, and
  > moving away from them in this manner is a definite plus.
Actually I just went back and looked at the archives and the source;
and f2c.h is not installed outside of $prefix by default.  It is only
done if F2C_INSTALL_FLAGS is true, which should only happen if
you've touched the file f2c-install-ok.

So, I think we need to find out how/why this file is being installed
on your systems and fix it.



Jeff

Re: Bug in installation

[Knut-HÃ¥vard Aksnes]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1987 bytes --]

Jeffrey A Law writes:
 > 
 >   In message <9712052020.AA29379@kona.>you write:
 >   > >>>>> "Jeffrey" == Jeffrey A Law <law@cygnus.com> writes:
 >   > 
 >   >  Jeffrey> Or maybe we stop installing f2c outside of $(libsubdir) and
 >   >  Jeffrey> instead have configure issue a warning about the existance
 >   >  Jeffrey> of an old f2c in /usr/include or /usr/local/include?


I second this comment.

 >   > 
 >   > Sounds like a great idea.  Hardwired destinations are a pain, and
 >   > moving away from them in this manner is a definite plus.
 > Actually I just went back and looked at the archives and the source;
 > and f2c.h is not installed outside of $prefix by default.  It is only
 > done if F2C_INSTALL_FLAGS is true, which should only happen if
 > you've touched the file f2c-install-ok.
 > 
 > So, I think we need to find out how/why this file is being installed
 > on your systems and fix it.
 > 
From my Makefile (This to debug the Makefile.in):
F2C_INSTALL_FLAG = [ -f f2c-install-ok -o -f $(srcdir)/f2c-install-ok ]

and later:

install-f2c-header:
        -if test -n "$(F2C_INSTALL_FLAG)" && test -f include/f2c.h; then \
          $(INSTALL_DATA) include/f2c.h $(includedir)/f2c.h; \
          chmod a+r $(includedir)/f2c.h; \
        else true; fi


What you wants is probably:

install-f2c-header:
        -if $(F2C_INSTALL_FLAG) && test -f include/f2c.h; then \
          $(INSTALL_DATA) include/f2c.h $(includedir)/f2c.h; \
          chmod a+r $(includedir)/f2c.h; \
        else true; fi

I   still  thinks  this is  the   wrong  way  of doing   installation,
enable/disable at configuration time  is probably better than checking
for f2c-install-ok.  (A warning can be  issued at configuration and/or
install time.)

---------------------------------------------------------------------------
Name:	Knut-HÃ¥vard Aksnes		Ericsson signature: HI/ETO/X/I KNA
Phones: Job: +47 370 51 481 		Mobile: +47 915 60 624
Email: etokna@eto.ericsson.se		Memo:  	ETO.ETOKNA