Wireshark-dev: Re: [Wireshark-dev] nmake setup target failing for me
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: Graham Bloice <graham.bloice@xxxxxxxxxxxxx>
Date: Thu, 9 Apr 2015 16:07:34 +0100
In my Wireshark dev VM's, I don't have Cygwin on the path at all, but then I don't use anything in Cygwin for tasks outside of the Wireshark build.

nmake builds pick the path up as configured in config.nmake (there are a number of defaults that are checked, and CMake does it's own search thing.

If you must have Cygwin on the path then it should be in the appropriate spot for you, i.e. should you want to use Cygwin executable rather than an identically named Windows version, then Cygwin will have to be in the path before System32.

I would remove any wget from System32.  Do you know how it got in there?
I have come across some applications that rely on Cygwin internally (usually ports of posix tools) and some very old ones did naughtily ram things in to System32.


On 9 April 2015 at 15:52, Martin Mathieson <martin.r.mathieson@xxxxxxxxxxxxxx> wrote:
Indeed I have seen the problems with copying Cygwin DLLs to Windows folders.

I don't currently have C:\cygwin\bin in my Windows PATH:
- is it safe to add it ahead of C:\Windows\System32?
- or would you recommend deleting the wget.exe from there so that it'll use the cygwin wget.exe instead?

Thanks,
Martin

On Thu, Apr 9, 2015 at 3:35 PM, Graham Bloice <graham.bloice@xxxxxxxxxxxxx> wrote:
You should never, ever have Cywgin DLL's or executables in System 32.  Source of much misery.

They should all live in their own bin dir, appropriate for the Cygwin installation.  You can even have multiple Cygwin installations if you're careful to keep the paths appropriate for the applications using them.



On 9 April 2015 at 15:24, Martin Mathieson <martin.r.mathieson@xxxxxxxxxxxxxx> wrote:
Hi Pascal,

I am running Windows Enterprise 7.0 with service pack 1.  It should be up to date with patches, but it may be a week or 2 since I rebooted it.

I did have both the (later version) cygwin wget.exe and what looks like the same, older version in 4 different places.  After replacing the one in C:\Windows\System32 with the Cygwin one, it grumbled about cygwin1.dll and cyggnutls-28.dll, which I'd rather not install.

There was no problem with browsing to the folder with the library files, and for now I have downloaded zip128.zip manually.
Martin


On Thu, Apr 9, 2015 at 2:47 PM, Pascal Quantin <pascal.quantin@xxxxxxxxx> wrote:
2015-04-09 15:28 GMT+02:00 Martin Mathieson <martin.r.mathieson@xxxxxxxxxxxxxx>:
I was prompted to run setup, but am getting this.  Any ideas?
Martin


****** zlib128.zip ******
No HTTP proxy specified (http_proxy and HTTP_PROXY are empty).
Downloading zlib128.zip into '/cygdrive/c/Wireshark-win32-libs', installing into
 .
/packages/zlib128.zip
           => `zlib128.zip'
Resolving anonsvn.wireshark.org... 174.137.42.70
Connecting to anonsvn.wireshark.org|174.137.42.70|:443... connected.
ERROR: Certificate verification error for anonsvn.wireshark.org: unable to get l
ocal issuer certificate
To connect to anonsvn.wireshark.org insecurely, use `--no-check-certificate'.
Unable to establish SSL connection.

15-04-06/packages/zlib128.zip


Hi Martin,

 I do not have any issue on my side. As anonsvn is using a SHA256 certificate, it suggests that your local host does not have the intermediate certificate installed, or deoes not support SHA256. On which Windows version are you running, and is it up-to-date with the latest Windows patch applied? According to http://blogs.technet.com/b/pki/archive/2013/11/12/sha1-deprecation-policy.aspx depending on the version you run, you might require some hotfixes applied.
As a workaround, you can edit win-setup.sh so as to add the --no-check-certificate option as suggested by the output message.

Pascal.

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe


___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe



--
Graham Bloice
Software Developer
Trihedral UK Limited

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe


___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe



--
Graham Bloice
Software Developer
Trihedral UK Limited