This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Fwd: Problem executing m4 (127 error, but it is installed)
- From: Kizito Porta Balanyà <kfeina at gmail dot com>
- To: cygwin at cygwin dot com
- Date: Wed, 26 Aug 2015 19:04:05 +0200
- Subject: Re: Fwd: Problem executing m4 (127 error, but it is installed)
- Authentication-results: sourceware.org; auth=none
- References: <CAO2ddnaqsmqfFfsFHTo4eHZrCDgwoAhDwMyT_6apfRNtN6NdKQ at mail dot gmail dot com> <55DDDED1 dot 7000701 at redhat dot com> <CAO2ddnZ_OxFjvRDH1knz_XBt6ZhXk8X0Az=pGXq2gSPgBRNB-g at mail dot gmail dot com> <CAO2ddnZdfj_0-sTAu2uYvjZutdYf-dKuKz+rKpG_bhJTmPda-g at mail dot gmail dot com> <55DDE95A dot 10305 at redhat dot com>
2015-08-26 18:29 GMT+02:00 Eric Blake <eblake@redhat.com>:
> On 08/26/2015 10:11 AM, Kizito Porta Balanyà wrote:
>>> Probably a missing dll. What does:
>>>
>>> cygcheck m4
>>>
>>> state? I'm guessing you may be missing libsigsegv2, which would show up
>>> as 'cygcheck: track_down: could not find cygsigsegv-2.dll'? If so,
>>> rerun setup.exe to install it (however, the m4 dependencies should
>>> automatically be pulling it in).
>>
>> cygcheck returns no error (no missing cygsigsegv-2.dll):
>
> Bummer, then something else is wrong.
>
>>
>> $ cygcheck m4
>> Found: C:\Windows\KSR\bin\m4.exe
>> Found: C:\Windows\KSR\bin\m4.exe
>> C:\Windows\KSR\bin\m4.exe
>> C:\Windows\KSR\bin\cygwin1.dll
> ...
>> C:\Windows\KSR\bin\cygsigsegv-2.dll
>
> Looks like the executable is fine, then. Maybe it's a virus scanner
> interfering, even though you said you've exempted things? Also, are you
> sure you are getting the correct m4? What does:
Sure, cygwin folder is excluded, but Symantec is Symantec.
Due that I can't stop Symantec via services, I rebooted the server and
now m4 works as expected.
Sorry again for the inconvenience. Thanks to your information I
discovered what passed.
Thanks a lot again.
Regards.
>
> $ type m4
>
> say? What about trying to execute it by absolute path:
>
> $ /bin/m4 --version
> $ /cygdrive/c/Windows/KSR/bin/m4 --version
>
> Could it be a collision between a non-executable file named 'm4' vs. the
> normal 'm4.exe' that is confusing cygwin .exe magic? Are you sure that
> nothing is messing with PATH and picking up a bogus m4 earlier in the
> lookup process?
>
> --
> Eric Blake eblake redhat com +1-919-301-3266
> Libvirt virtualization library http://libvirt.org
>
--
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