Re: 1.7.x: m4 does not show any reaction

Marcus Osdoba Wed, 17 Nov 2010 12:27:01 -0800

Am 17.11.2010 20:29, schrieb Eric Blake:

On 11/17/2010 12:06 PM, Marcus Osdoba wrote:

Dear cygwin mailinglist,


I'm trying to use m4 (from Interpreters m4 package) in cygwin 1.7.
The executable does not show any reaction when I launch
/usr/bin/m4(.exe) --version or --help or some.m4

My guess is that you're missing a dependent .dll; probably libsigsegv.
What does:

cygcheck /bin/m4

say?

Hi,

Many thanks for the quick answer. Yes, you are right. There is nocygsigseg-dll in the launch profile:



$ cygcheck /bin/m4
C:\cygwin\bin\m4.exe
  C:\cygwin\bin\cygwin1.dll
    C:\Windows\system32\ADVAPI32.DLL
      C:\Windows\system32\msvcrt.dll
        C:\Windows\system32\KERNELBASE.dll
          C:\Windows\system32\ntdll.dll
        C:\Windows\system32\API-MS-Win-Core-Console-L1-1-0.dll
        C:\Windows\system32\API-MS-Win-Core-DateTime-L1-1-0.dll
        C:\Windows\system32\API-MS-Win-Core-Debug-L1-1-0.dll
        C:\Windows\system32\API-MS-Win-Core-ErrorHandling-L1-1-0.dll
        C:\Windows\system32\API-MS-Win-Core-Fibers-L1-1-0.dll
        C:\Windows\system32\API-MS-Win-Core-File-L1-1-0.dll
        C:\Windows\system32\API-MS-Win-Core-Handle-L1-1-0.dll
        C:\Windows\system32\API-MS-Win-Core-Heap-L1-1-0.dll
        C:\Windows\system32\API-MS-Win-Core-Interlocked-L1-1-0.dll
        C:\Windows\system32\API-MS-Win-Core-Localization-L1-1-0.dll
        C:\Windows\system32\API-MS-Win-Core-LibraryLoader-L1-1-0.dll
        C:\Windows\system32\API-MS-Win-Core-Memory-L1-1-0.dll
        C:\Windows\system32\API-MS-Win-Core-Misc-L1-1-0.dll
        C:\Windows\system32\API-MS-Win-Core-NamedPipe-L1-1-0.dll
        C:\Windows\system32\API-MS-Win-Core-ProcessEnvironment-L1-1-0.dll
        C:\Windows\system32\API-MS-Win-Core-ProcessThreads-L1-1-0.dll
        C:\Windows\system32\API-MS-Win-Core-Profile-L1-1-0.dll
        C:\Windows\system32\API-MS-Win-Core-String-L1-1-0.dll
        C:\Windows\system32\API-MS-Win-Core-Synch-L1-1-0.dll
        C:\Windows\system32\API-MS-Win-Core-SysInfo-L1-1-0.dll
        C:\Windows\system32\API-MS-Win-Core-Util-L1-1-0.dll
      C:\Windows\system32\API-MS-WIN-Service-Core-L1-1-0.dll
      C:\Windows\system32\API-MS-WIN-Service-winsvc-L1-1-0.dll
      C:\Windows\system32\API-MS-WIN-Service-Management-L1-1-0.dll
      C:\Windows\system32\API-MS-WIN-Service-Management-L2-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-LocalRegistry-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Security-Base-L1-1-0.dll
      C:\Windows\system32\KERNEL32.dll
        C:\Windows\system32\API-MS-Win-Core-RtlSupport-L1-1-0.dll
        C:\Windows\system32\API-MS-Win-Core-IO-L1-1-0.dll
        C:\Windows\system32\API-MS-Win-Core-ThreadPool-L1-1-0.dll
      C:\Windows\system32\RPCRT4.dll
        C:\Windows\system32\SspiCli.dll
          C:\Windows\system32\CRYPTBASE.dll
            C:\Windows\system32\API-MS-Win-Core-DelayLoad-L1-1-0.dll
          C:\Windows\system32\API-MS-Win-Security-LSALookup-L1-1-0.dll
  C:\cygwin\bin\cyggcc_s-1.dll

I maintain upstream m4 and build on cygwin all the time, with no
problems on my end.

Is it somehow possible to make m4 dependent on cygsigseg? So it wouldn'tbe possible to install it without it (like I did...).


Thanks again,
Ossy


--
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

Re: 1.7.x: m4 does not show any reaction

Reply via email to