What DLLs does my cygwin built .exe need ?

If you have built a unix tool under cygwin, how do you know what DLLs are needed when you want to give someone the executable file you have built ?

cygcheck is your friend

Here we can see 3 DLLs would be needed to accompany the iperf.exe that I have built.

   1:  C:\temp>\cygwin\bin\cygcheck iperf-gf.exe

   2:  Found: iperf-gf.exe

   3:  iperf-gf.exe

   4:    c:\cygwin\bin\cygwin1.dll

   5:      C:\WINDOWS\system32\ADVAPI32.DLL

   6:        C:\WINDOWS\system32\KERNEL32.dll

   7:          C:\WINDOWS\system32\ntdll.dll

   8:        C:\WINDOWS\system32\RPCRT4.dll

   9:          C:\WINDOWS\system32\Secur32.dll

  10:    c:\cygwin\bin\cyggcc_s-1.dll

  11:    c:\cygwin\bin\cygstdc++-6.dll

.csharpcode, .csharpcode pre
{
font-size: small;
color: black;
font-family: consolas, “Courier New”, courier, monospace;
background-color: #ffffff;
/*white-space: pre;*/
}
.csharpcode pre { margin: 0em; }
.csharpcode .rem { color: #008000; }
.csharpcode .kwrd { color: #0000ff; }
.csharpcode .str { color: #006080; }
.csharpcode .op { color: #0000c0; }
.csharpcode .preproc { color: #cc6633; }
.csharpcode .asp { background-color: #ffff00; }
.csharpcode .html { color: #800000; }
.csharpcode .attr { color: #ff0000; }
.csharpcode .alt
{
background-color: #f4f4f4;
width: 100%;
margin: 0em;
}
.csharpcode .lnum { color: #606060; }
.csharpcode, .csharpcode pre
{
font-size: small;
color: black;
font-family: consolas, “Courier New”, courier, monospace;
background-color: #ffffff;
/*white-space: pre;*/
}
.csharpcode pre { margin: 0em; }
.csharpcode .rem { color: #008000; }
.csharpcode .kwrd { color: #0000ff; }
.csharpcode .str { color: #006080; }
.csharpcode .op { color: #0000c0; }
.csharpcode .preproc { color: #cc6633; }
.csharpcode .asp { background-color: #ffff00; }
.csharpcode .html { color: #800000; }
.csharpcode .attr { color: #ff0000; }
.csharpcode .alt
{
background-color: #f4f4f4;
width: 100%;
margin: 0em;
}
.csharpcode .lnum { color: #606060; }

 

ie. cygwin1.dll, cyggcc_s-1.dll and cygstdc+-6.dll

WordPress page.php is for a static non-blog PAGE, index.php is for a blog POST

If you want to change the look and feel of a PAGE to wordpress, you will want to look at page.php. This is the template file for the theme you have selected, located in the themes directory /wp-content/themes/UR_THEME/page.php

If you want to change the look and feel of a BLOG POST, index.php is your man.

In WordPress, a PAGE does not have categories but can have comments.

A POST can have categories and tags and comments.

Typically you would use a POST to create a new blog item and a PAGE to create a static web page like About or Contact ME.

Compiling iperf under cygwin (iperf.exe win32)

Use the setup.exe that is part of cygwin to select and install the official iPerf packages for cygwin.

iPerf is included in the net group. Select the src box too if you want that.

After it has run, you can find the files in /usr/src

Follow the instructions to extract the distribution using

   1:  cd /usr/src

   2:   

   3:  cygport iperf-2.0.4-1.cygport all

   4:   

   5:  cd /usr/src/iperf-2.0.4-1/src/iperf-2.0.4

   6:   

   7:  ./configure

   8:   

   9:  ./make

  10:   

.csharpcode, .csharpcode pre
{
font-size: small;
color: black;
font-family: consolas, “Courier New”, courier, monospace;
background-color: #ffffff;
/*white-space: pre;*/
}
.csharpcode pre { margin: 0em; }
.csharpcode .rem { color: #008000; }
.csharpcode .kwrd { color: #0000ff; }
.csharpcode .str { color: #006080; }
.csharpcode .op { color: #0000c0; }
.csharpcode .preproc { color: #cc6633; }
.csharpcode .asp { background-color: #ffff00; }
.csharpcode .html { color: #800000; }
.csharpcode .attr { color: #ff0000; }
.csharpcode .alt
{
background-color: #f4f4f4;
width: 100%;
margin: 0em;
}
.csharpcode .lnum { color: #606060; }

will then all work just like it does under a unix proper, you will get an iperf.exe in the src directory.

The iperf binary will also get installed in /usr/bin/

Reducing SPAM links on wordpress blog comments–remove url in form

On my main wordpress blog I run Akismet to detect SPAM comments. This is the first line of defence

Next I also run WordPress HashCash which forces commenters to be running javascript on the web page before they can leave a comment. The JS requires a sum to be calculated, and if it doesn’t match the required value you know that it is likely that it isn’t a human using a web browser trying to leave a comment. Probably it is a spammer doing bulk POST request to sites all over the net.

Lately this regime has been letting a few through each day.

This is unusual, but shows that spammers are now willing to pay real humans to sit down and leave comments on blogs.

So the next step I’m trying now is to remove the URL from the comment form. This will make it harder to leave a web address in the usual way. They can still POST this field, but only from a hacked browser or javascript aware bot.

It killed spam comments dead for the last few days. So far so good.

My web site visitors (not here, the self hosted one that I haven’t linked to) tend to be not be computer enthusiasts, so don’t have their own blog to legitimately link to, so I don’t think they will care.

Keeping notes here now.

Thought I might post little snippets of stuff as I think of them here now. That way I can search for them later. Be prepared, this blog is about to get weird and hard to follow.