* Problem executing m4 (127 error, but it is installed)
@ 2015-08-26 16:11 Kizito Porta Balanyà
2015-08-26 16:29 ` Eric Blake
0 siblings, 1 reply; 5+ messages in thread
From: Kizito Porta Balanyà @ 2015-08-26 16:11 UTC (permalink / raw)
To: cygwin
Hello,
I'm trying to build MONIT, but with the new version of cygwin, I need m4.
I have installed it, but when running it, I get a 127 error:
$cd /usr/bin
$ m4
$ echo $?
127
To test that really m4 exists, I try m5:
$m5
-bash: m5: command not found
It is a little strange, Antivirus is configured to no scan the cygwin unit.
I'm usuing, CYGWIN_NT-6.3 MYHOSTNAME 2.0.1(0.287/5/3) 2015-04-30 18:15
x86_64 Cygwin
Do you have any idea ? Can you help me?
Thanks a lot for your time
--
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Problem executing m4 (127 error, but it is installed)
2015-08-26 16:11 Problem executing m4 (127 error, but it is installed) Kizito Porta Balanyà
@ 2015-08-26 16:29 ` Eric Blake
[not found] ` <CAO2ddnZ_OxFjvRDH1knz_XBt6ZhXk8X0Az=pGXq2gSPgBRNB-g@mail.gmail.com>
0 siblings, 1 reply; 5+ messages in thread
From: Eric Blake @ 2015-08-26 16:29 UTC (permalink / raw)
To: cygwin; +Cc: kfeina
[-- Attachment #1: Type: text/plain, Size: 673 bytes --]
On 08/26/2015 09:26 AM, Kizito Porta Balanyà wrote:
> Hello,
>
> I'm trying to build MONIT, but with the new version of cygwin, I need m4.
>
> I have installed it, but when running it, I get a 127 error:
>
> $cd /usr/bin
> $ m4
> $ echo $?
> 127
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).
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Fwd: Problem executing m4 (127 error, but it is installed)
[not found] ` <CAO2ddnZ_OxFjvRDH1knz_XBt6ZhXk8X0Az=pGXq2gSPgBRNB-g@mail.gmail.com>
@ 2015-08-26 17:04 ` Kizito Porta Balanyà
2015-08-26 19:28 ` Eric Blake
0 siblings, 1 reply; 5+ messages in thread
From: Kizito Porta Balanyà @ 2015-08-26 17:04 UTC (permalink / raw)
To: cygwin
2015-08-26 17:44 GMT+02:00 Eric Blake <eblake@redhat.com>:
> On 08/26/2015 09:26 AM, Kizito Porta Balanyà wrote:
>> Hello,
>>
>> I'm trying to build MONIT, but with the new version of cygwin, I need m4.
>>
>> I have installed it, but when running it, I get a 127 error:
>>
>> $cd /usr/bin
>> $ m4
>> $ echo $?
>> 127
>
> 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):
$ 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\system32\KERNEL32.dll
C:\Windows\system32\api-ms-win-core-rtlsupport-l1-2-0.dll
C:\Windows\system32\ntdll.dll
C:\Windows\system32\KERNELBASE.dll
C:\Windows\system32\api-ms-win-core-apiquery-l1-1-0.dll
C:\Windows\system32\api-ms-win-core-processthreads-l1-1-2.dll
C:\Windows\system32\api-ms-win-core-registry-l1-1-0.dll
C:\Windows\system32\api-ms-win-core-heap-l1-2-0.dll
C:\Windows\system32\api-ms-win-core-memory-l1-1-2.dll
C:\Windows\system32\api-ms-win-core-handle-l1-1-0.dll
C:\Windows\system32\api-ms-win-core-synch-l1-2-0.dll
C:\Windows\system32\api-ms-win-core-file-l1-2-1.dll
C:\Windows\system32\api-ms-win-core-delayload-l1-1-1.dll
C:\Windows\system32\api-ms-win-core-io-l1-1-1.dll
C:\Windows\system32\api-ms-win-core-job-l1-1-0.dll
C:\Windows\system32\api-ms-win-core-threadpool-legacy-l1-1-0.dll
C:\Windows\system32\api-ms-win-core-threadpool-private-l1-1-0.dll
C:\Windows\system32\api-ms-win-core-libraryloader-l1-2-0.dll
C:\Windows\system32\api-ms-win-core-namedpipe-l1-2-0.dll
C:\Windows\system32\api-ms-win-core-datetime-l1-1-1.dll
C:\Windows\system32\api-ms-win-core-sysinfo-l1-2-1.dll
C:\Windows\system32\api-ms-win-core-timezone-l1-1-0.dll
C:\Windows\system32\api-ms-win-core-localization-l1-2-1.dll
C:\Windows\system32\api-ms-win-core-processenvironment-l1-2-0.dll
C:\Windows\system32\api-ms-win-core-string-l1-1-0.dll
C:\Windows\system32\api-ms-win-core-debug-l1-1-1.dll
C:\Windows\system32\api-ms-win-core-errorhandling-l1-1-1.dll
C:\Windows\system32\api-ms-win-core-fibers-l1-1-1.dll
C:\Windows\system32\api-ms-win-core-util-l1-1-0.dll
C:\Windows\system32\api-ms-win-core-profile-l1-1-0.dll
C:\Windows\system32\api-ms-win-security-base-l1-2-0.dll
C:\Windows\system32\api-ms-win-security-appcontainer-l1-1-0.dll
C:\Windows\system32\api-ms-win-core-comm-l1-1-0.dll
C:\Windows\system32\api-ms-win-core-realtime-l1-1-0.dll
C:\Windows\system32\api-ms-win-core-wow64-l1-1-0.dll
C:\Windows\system32\api-ms-win-core-systemtopology-l1-1-0.dll
C:\Windows\system32\api-ms-win-core-processtopology-l1-2-0.dll
C:\Windows\system32\api-ms-win-core-namespace-l1-1-0.dll
C:\Windows\system32\api-ms-win-core-file-l2-1-1.dll
C:\Windows\system32\api-ms-win-core-xstate-l2-1-0.dll
C:\Windows\system32\api-ms-win-core-localization-l2-1-0.dll
C:\Windows\system32\api-ms-win-core-normalization-l1-1-0.dll
C:\Windows\system32\api-ms-win-core-localization-private-l1-1-0.dll
C:\Windows\system32\api-ms-win-core-sidebyside-l1-1-0.dll
C:\Windows\system32\api-ms-win-core-appcompat-l1-1-1.dll
C:\Windows\system32\api-ms-win-core-windowserrorreporting-l1-1-0.dll
C:\Windows\system32\api-ms-win-core-console-l1-1-0.dll
C:\Windows\system32\api-ms-win-core-console-l2-1-0.dll
C:\Windows\system32\api-ms-win-core-psapi-l1-1-0.dll
C:\Windows\system32\api-ms-win-core-psapi-ansi-l1-1-0.dll
C:\Windows\system32\api-ms-win-core-psapi-obsolete-l1-1-0.dll
C:\Windows\KSR\bin\cygsigsegv-2.dll
Can you help me?
I just installed openssl-devel and monit's compilation started to fail
(perhaps this information can help)
Thanks a lot.
> --
> 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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Fwd: Problem executing m4 (127 error, but it is installed)
2015-08-26 17:04 ` Fwd: " Kizito Porta Balanyà
@ 2015-08-26 19:28 ` Eric Blake
2015-08-26 19:50 ` Kizito Porta Balanyà
0 siblings, 1 reply; 5+ messages in thread
From: Eric Blake @ 2015-08-26 19:28 UTC (permalink / raw)
To: cygwin, Kizito Porta Balanyà
[-- Attachment #1: Type: text/plain, Size: 1368 bytes --]
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:
$ 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
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Fwd: Problem executing m4 (127 error, but it is installed)
2015-08-26 19:28 ` Eric Blake
@ 2015-08-26 19:50 ` Kizito Porta Balanyà
0 siblings, 0 replies; 5+ messages in thread
From: Kizito Porta Balanyà @ 2015-08-26 19:50 UTC (permalink / raw)
To: cygwin
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
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2015-08-26 17:04 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-08-26 16:11 Problem executing m4 (127 error, but it is installed) Kizito Porta Balanyà
2015-08-26 16:29 ` Eric Blake
[not found] ` <CAO2ddnZ_OxFjvRDH1knz_XBt6ZhXk8X0Az=pGXq2gSPgBRNB-g@mail.gmail.com>
2015-08-26 17:04 ` Fwd: " Kizito Porta Balanyà
2015-08-26 19:28 ` Eric Blake
2015-08-26 19:50 ` Kizito Porta Balanyà
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).