DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=IBAuQcGARwvd5Asq
	nLYIsLHlHgFleyCGGQAUTuFfGxRN9gXnVDYIIGIPA2l3YvhThSJ4gUW/u3lFSBSZ
	yAfjrlEwOJPX/azQON8lePey03a65Ashn/EL1b6u6JXNyK7LlGQnagiQFvmUKNPF
	llUMIqGed8J7rJRTkNHDy3AlkmE=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Subject: Re: Autoconf fooled by AC_FC_LINE_LENGTH
To: cygwin AT cygwin DOT com
References: <8fa2a8a5-fb86-02c9-5cd0-521a9680abe3 AT gmail DOT com> <d9a1d5a2-f477-c14a-db23-bfa9334308fa AT lysator DOT liu DOT se>
From: Marco Atzeri <marco DOT atzeri AT gmail DOT com>
Message-ID: <f99e8aa5-c077-f60b-3e19-bd9c6f2fb242@gmail.com>
Date: Sat, 30 Jul 2016 06:23:36 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <d9a1d5a2-f477-c14a-db23-bfa9334308fa@lysator.liu.se>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

On 29/07/2016 21:32, Peter Rosin wrote:
> On 2016-07-29 14:23, Marco Atzeri wrote:
>> Hi Eric,
>>
>> building latest Arpack
>> https://github.com/opencollab/arpack-ng/releases
>> https://github.com/opencollab/arpack-ng/issues/41
>>
>> I hit a strange case where the presence of a single line
>>
>> AC_FC_LINE_LENGTH(unlimited)
>>
>> before the usual
>> LT_PREREQ([2.4.2])
>> LT_INIT([win32-dll])
>>
>> is causing the libtool to be incorrectly set, versus
>> the right case

>>
>> It seems libtool is incorrectly set for MSVC platform
>>
>> I tried to move the libtool inizialization before the
>> AC_FC_LINE_LENGTH but autoconf is objecting on wrong preference.
>>
>> It seems a bug impacting only cygwin.
>
> Reading the source comment for AC_FC_LINE_LENGTH indicates that
> you should call AC_FC_FREEFORM or AC_FC_FIXEDFORM before you call
> AC_FC_LINE_LENGTH. You do not do that. This is not mentioned in
> the autoconf manual I'm looking at. I don't know if the source
> code comment or the manual is correct (it's been 20 years since I
> last used fortran...)

Hi Peter,
thanks for the hint, unfortunately it makes no difference.

Looking at the upstream code I notice
that AC_FC_LINE_LENGTH is the only FC call
while all the rest is F77 based

$ grep _FC configure.ac
   AC_FC_LINE_LENGTH(unlimited)

$ grep _F77 configure.ac
AC_PROG_F77
AC_F77_FUNC(sgemm$SYMBOLSUFFIX, sgemmsuff)
AC_F77_FUNC(snaupd$SYMBOLSUFFIX, snaupdsuff)
AC_F77_FUNC(sneupd$SYMBOLSUFFIX, sneupdsuff)
AC_F77_FUNC(dnaupd$SYMBOLSUFFIX, dnaupdsuff)
AC_F77_FUNC(dneupd$SYMBOLSUFFIX, dneupdsuff)
AC_F77_FUNC(cheev$SYMBOLSUFFIX, cheevsuff)

and this is fishy.
I need to check it

>
> However, I suspect the issue is that libtool might eat or be
> otherwise confused by the flag selected to get fortran support
> for long lines. What is FCFLAGS when you have the macro present?
>
> Out on a limb here...
>
> Cheers,
> Peter
>
> PS. some logs would be handy...

which one ? Autoconf and configure are a bit verbose

Regards
Marco


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple