[Pkg-octave-devel] Bug#434415: [kimhanse@gmail.com: Bug#434415: octave2.9-headers: Changed F77_FUNC_ macro]
On 7/24/07, John W. Eaton <jwe@bevo.che.wisc.edu> wrote:
On 24-Jul-2007, Thomas Weber wrote:
| Am Montag, 23. Juli 2007 22:12:14 schrieb Rafael Laboissiere:
| > ----- Forwarded message from Kim Hansen <kimhanse@gmail.com> -----
| >
| > From: Kim Hansen <kimhanse@gmail.com>
| > Subject: [Pkg-octave-devel] Bug#434415: octave2.9-headers: Changed
| > F77_FUNC_ macro
| > Date: Mon, 23 Jul 2007 19:51:13 +0200
| > To: Debian Bug Tracking System <submit@bugs.debian.org>
| > Reply-To: Kim Hansen <kimhanse@gmail.com>, 434415@bugs.debian.org
| > Message-ID: <[🔎] 20070723175113.23843.41346.reportbug@localhost.localdomain>
| >
| > Package: octave2.9-headers
| > Version: 1:2.9.12-2+b3
| > Severity: normal
| >
| >
| > I don't know if this is a real bug, but between version 2.9.10-4.1 and
| > 1:2.9.12-2+b3 has the definition of the macro F77_FUNC_ in
| > /usr/include/octave/config.h changed from
| > #define F77_FUNC_(name,NAME) name ## _
| > to
| > #define F77_FUNC_(name,NAME) name ## __
|
| If I read the output of
| cvs annotate configure.in
| correctly, John hasn't touched these lines for about 5 years. Could this be
| caused by our (=Debian) current mixture of g77 and gfortran?
If you mean these lines in the generated config.h file:
/* Define to a macro mangling the given C identifier (in lower and upper
case), which must not contain underscores, for linking with Fortran. */
#define F77_FUNC(name,NAME) name ## _
/* As F77_FUNC, but for C identifiers containing underscores. */
#define F77_FUNC_(name,NAME) name ## __
Yes, I am talking about the last one of those two lines.
In any case, we probably need to think about how to avoid installing
the generated config.h. We may still need a subset of that file
installed, but it should probably have a different name.
The reason I became aware of this change is a warning I get when
compiling an oct-file that uses an other library. This library also
uses fortran code and it also have an auto generated F77_FUNC_ macro,
the two macros are different, thus the warning.
Moving config.h away would silence the warning, and solve the problem
unless it was an important warning. But I don't know if it is, I know
too little about fortran linking, I was just curious about the change
in the macro.
Regards,
--
Kim Hansen
Vadgårdsvej 3, 2.tv
2860 Søborg
Fastnet: 3956 2437 -- Mobil: 3091 2437
Reply to: