text:
Interested in compiling wine from source? Want to submit some patches, run a bisection, or maybe just install a patch to make your favorite game work? You've come to the right place.
Before you compile a single line of ANSI C, there are a few things you need in order to build wine successfully.
Getting the Wine Source
You can download the Wine source code as a tarball from several places (including the Wine Download server), but if you plan to do any actual testing or developing, you'll want to use git. For more information and some useful hints, see Git Wine Tutorial and the Source Code wiki page.
To grab the source code to wine itself, just enter the following command, replacing the directory path at the end with whatever folder you want to download the source tree into:
git clone https://gitlab.winehq.org/wine/wine.git ~/wine-dirs/wine-source
If for some reason the git protocol is blocked on your network, try using the http URL instead (http://gitlab.winehq.org/wine/wine.git).
Satisfying Build Dependencies
Once you have the source code, it's time to grab all of the necessary build tools and libraries. If you have a unix with package management, probably the quickest way to find most of the software you need is to use whatever "build dependency" command your package manager offers.
Unfortunately, that by itself probably won't get everything. Dependencies for features you want may be marked as optional or not even packaged in your distro's repository. Wine is still evolving as a project too and might switch over to different libraries between versions, something that especially comes into play if you use a stable distro with spaced out releases.
Check out Category:Distributions to see if your distro has its own page, which may include more tips about dependencies and compiling there.
While Wine has many dependencies on external libraries, not all of them are actually necessary to build Wine, or indeed to run whatever program you're interested in running. The following table details Wine's build dependencies and what they are used for.
Library name | Debian | Fedora | Arch | Function | Notes |
Generally necessary | |||||
32-bit toolchain | gcc-multilib | glibc-devel.i686 | ? | Needed for 32-bit builds | |
MinGW cross-compiler | gcc-mingw-w64 | mingw32-gcc, mingw64-gcc | mingw-w64-gcc | PE format DLLs | |
ALSA | libasound2-dev | alsa-devel | alsa-lib | Sound backend | At least one is necessary for sound. |
PulseAudio | libpulse-dev | libpulse-devel | libpulse | ||
libdbus | libdbus-1-dev | dbus-libs | dbus | Dynamic device detection (specifically, mass storage) | Removable drives may be incorrectly detected otherwise. |
libfontconfig | libfontconfig-dev | fontconfig-devel | fontconfig | Host font enumeration | Install if you want host fonts to be detected. |
libfreetype | libfreetype-dev | freetype-devel | freetype2 | FreeType font reading | |
libgnutls | libgnutls28-dev | gnutls-devel | gnutls | Cryptography | |
libinotify | N/A | N/A | N/A | File change notification | Only necessary for some platforms (Linux does not need this.) |
OpenGL | libgl-dev | mesa-libGL-devel | mesa | Hardware-accelerated/3D graphics | |
libunwind | libunwind-dev | libunwind-devel | libunwind | Exception unwinding | Necessary for x86_64 and arm64, but not used on other platforms. |
libX11 | libx11-dev | libX11-devel | libx11 | Window management | |
XComposite | libxcomposite-dev | libXcomposite-devel | libxcomposite | Window drawing | |
XCursor | libxcursor-dev | libXcursor-devel | libxcursor | Cursor management | |
XFixes | libxfixes-dev | libXfixes-devel | libxfixes | Clipboard management | |
XInput 2 | libxi-dev | libXi-devel | libxi | Keyboard and mouse | |
XRandR | libxrandr-dev | libXrandr-devel | libxrandr | Display device management | |
XRender | libxrender-dev | libXrender-devel | libxrender | Window drawing | |
XShape, XShm | libxext-dev | libXext-devel | libxext | Window drawing | |
Needed for many applications | |||||
GStreamer 1.0 | libgstreamer1.0-dev, libgstreamer-plugins-base1.0-dev | gstreamer1-devel, gstreamer1-plugins-base-devel | gstreamer, gst-plugins-base-libs | Multimedia playback | Generally necessary for games or applications that play back audio or video files. |
OSMesa | libosmesa6-dev | libOSMesa-devel | mesa | OpenGL bitmap support | |
libSDL2 | libsdl2-dev | SDL2-devel | sdl2 | HID joystick support | Generally necessary for joystick or other HID support. Only one library is necessary, but they may exhibit different behaviour. |
libudev | libudev-dev | ? | systemd | ||
Vulkan | libvulkan-dev | vulkan-headers, libvulkan-loader | vulkan-icd-loader, vulkan-headers | Hardware-accelerated/3D graphics | Necessary for some games; only supported by some video cards. |
Rare or domain-specific | |||||
libcapi20 | libcapi20-dev | (none) | (none) | ISDN/telephony | Install only if you're using ISDN software. |
libcups | libcups2-dev | cups-devel | libcups | Printing | Install only if you need printer support. |
libgphoto2 | libgphoto2-dev | libgphoto2-devel | libgphoto2 | Scanner/still image | Install only if you're using scanner/still image software. |
libsane | libsane-dev | sane-backends-devel | sane | ||
Kerberos | libkrb5-dev | krb5-devel | krb5 | Kerberos authentication | Install only if you're connecting via Kerberos. |
libnetapi | samba-dev | samba-devel | smbclient | Networking | Rarely needed. |
OpenCL | ocl-icd-opencl-dev | ocl-icd-devel | ocl-icd | Parallel computing / GPGPU | Install if you're using parallel computing or GPGPU software. |
libpcap | libpcap-dev | libpcap-devel | libpcap | Packet capture | Install if you are using applications that require packet capture. (This replaces native wpcap.dll shipped by applications.) |
libusb 1.0 | libusb-1.0-0-dev | libusbx-devel | libusb | USB device support | Install only if you're using an application that accesses a USB device directly. (Note that many applications using USB devices do so through HID.) See also Hardware. |
libv4l2 | libv4l-dev | libv4l-devel | v4l-utils | Video capture | Install only if you're capturing video. |
Never necessary | |||||
XFree86-VM | libxxf86vm-dev | libXxf86vm-devel | libxxf86vm | Display management | Obsolete; use XRandR instead. |
Xinerama | libxinerama-dev | libXinerama-devel | libxinerama | Display management | Obsolete; use XRandR instead. |
libhal | (none) | (none) | (none) | Dynamic device detection | Obsolete; use libdbus instead. |
After using package management, the surest way to figure out exactly what dependencies you still need is to start the build process & run the configure script from wine's source directory:
./configure --options
(or from within a distinct build directory, but more about that in the next section):
relative-path/to-wine-source/configure --options
Glib2 and gstreamer have different header files for 32 and 64 bit, so when compiling 32 bit Wine with gstreamer support on a 64 bit system it is necessary to use PKG_CONFIG_PATH=/path/to/pkgconfig to point to the location of the 32 bit files when running ./configure. Without that, ./configure will find the 64 bit development files instead of the 32 bit ones and disable gstreamer support. (See https://www.winehq.org/pipermail/wine-devel/2016-January/111245.html)
If you're missing a library or program wine needs to build, the script should output a message specifically telling you what you still need to install. Ideally one run through the configure script would list all the missing software, but at least for now, the script terminates at the first check it fails. If you persist through the cycle (tedious, I know) of configure, install missing software, repeat, the script should finish and display a success message.
By the way, some features of wine (legacy, experimental, etc.) aren't enabled by default but can still be built into wine with the right libraries. On a successful run, the configure script should list all disabled features and which libraries enable them. To include those features, simply install the relevant libraries, then run the configure script one more time.
Runtime Dependencies
If you actually want to run wine after you build it, you'll also need to install runtime dependencies too. The simplest way to do this for most systems is to install the wine release provided by your distro, along with all of its dependencies. Of course, if you use a very old distro, this might not work without forcing an upgrade for many of the dependencies.
Once you do have all dependencies installed, as long as you give your custom wine build its own wine-prefix, you should be able to run it (from inside the build directory) alongside the official repo version without conflicts.
If you would rather uninstall your distro's version of wine, you have a few options for what to do after uninstalling it:
- Just leave the dependencies alone. The main problem with this is your package manager might mark them as unnecessary, orphaned, autoremovable, etc.
- Mark the dependencies as manually installed through your package manager. This approach only causes problems if you want to entirely remove wine and its dependencies from your system later; a command such as autoremove won't uninstall packages marked as manually installed.
- Package your custom version of wine for installation. This definitely involves the most work, but should keep your package database consistent.
Plain Vanilla Compiling
If you plan to run Wine on the same 32-bit architecture that you're building it on, then you're in luck; things should be very simple.
If you just want to build Wine on common hardware with a 64-bit distro, odds are you want a WoW64 build.
With all the build requirements installed:
- Change into whatever directory you would like to build wine inside
- From there, invoke the configure script in your wine source directory
- After that, run make inside your build directory
- If make finishes successfully, you can install wine into your system with make install
On the command line:
cd ~/wine-dirs/wine-build/ ../wine-source/configure make make install
The last step is purely at your discretion; you can run wine entirely from within the build directory without installation. If you do install wine through make, just be sure that you don't have a version of wine already installed. Overlapping installations shouldn't break your system, but they might seriously tangle up your libraries and package management.
Configure Options
If you're on a 64-bit system, all you need to do to build a 64-bit wine is pass --enable-win64 to the configure script when you run the above commands:
../wine-source/configure --enable-win64
The problem is that by itself, that build will only run applications compiled for 64-bit Windows. Since the vast majority of Windows applications are 32-bit, you very likely want to follow the WoW64 instructions below.
If you want to explicitly leave out an optional feature, even if you have its dependencies installed, the configure script has many options (--without-PACKAGE) to disable certain libraries. There are also some options to force including libraries that normally aren't by default (--with-PACKAGE). A second class of options can be used to disable or enable general features in wine (--disable-FEATURE and --enable-FEATURE).
If you plan on cross-compiling to a completely different architecture (not just 32-bit wine on a 64-bit system), you'll definitely want the --with-wine-tools= option. When you type it, just add the relative path to the tools subdirectory of a wine build compiled for your host system. Unless you include this option (or a copy of the tools are cached where the build scripts can see them), the configure script will abort with an error if you also pass a cross-compiling option.
The configure script has a help flag (-h) that lists all relevant options and environment variables, along with a short description. The script also recognizes tab-completion so for a simple list of supported options, just type two hyphens after the configure command and hit tab a couple times.
If for any reason you need to pass flags to the compiler while building wine, you can set them with the CFLAGS environment variable during configuration.
General Compiling Hints
You're perfectly free to build and install wine from within the source directory, but using a separate build directory has many advantages. It keeps the source code uncluttered, makes testing distinct builds easier, allows for much cleaner cross-compilation, simplifies chroots or linux containers, etc.
Just getting started with building software on unix? You might have heard of make clean. The wine makefiles also include this rule, which will automatically clean out all the intermediate object files from the build directory. However, those same object files are how make knows what steps it can skip if you change the source code and recompile. So if you don't want to recompile all of wine from scratch after every patch, don't disturb the object files.
Maybe you've got one of those (so radically winning) solid-state drives, and you're wondering if compiling on your solid-state drive helps at all. A cruise around the internet shows mixed opinions. If you do see improvements, they'll likely be insignificant and mostly come from faster read times on the source files (processing power is the main bottleneck for compilers). At the same time, while it's not as much an issue as it used to be, solid-state drives are capable of a fixed number of write operations before wearing out. If you really want to, there are ways to have your compiler read the source code from SSD, write the temporary build files into a directory on hard-disk (or even RAM), and even move the finished program back onto the SSD (see how cool separate build directories are?)
Instead of looking for a SSD to speedup your compile times, consider installing ccache if you'll be building from source repeatedly. Even with make, it adds more sophisticated caching that can be shared across directories. For a small time penalty during your first build, it can cut compile times significantly. Unless you're using another wrapper to your compiler (which makes things more complicated), you only need to set the CC environment variable to call your compiler from ccache, which can also be done specifically for your wine build when calling the configure script. For example, if you're using GCC:
../wine-source/configure CC="ccache gcc" CROSSCC="ccache i686-w64-mingw32-gcc" #your usual configure options
Be sure to replace i686 with x86_64 for 64-bit builds. If you have a multi-core processor, the make command has a couple of flags you might like.
- The -j flag tells make to try running independent recipes on different cores with maximum parallelism; an alternate form -jN will start up to N recipes in parallel:
make -j5
- Another option is the -l F.F flag, which only starts more recipes in parallel so long as the average system load doesn't exceed the floating-point number F.F.
- These features don't work for all projects, but they're designed to fail gracefully and revert to serial building when that happens.
- If you don't want to use your computer for anything else while building, a common rule-of-thumb is to set N in -jN to (the number of cores on your system + 1) (the idea behind the extra job is to keep all cores running even when one pauses for IO requests).
- The parallelism in make usually shows diminishing marginal speed-up so if you want to work on your computer while building, don't hesitate to save yourself a few cores.
- Using configure cache using passing -C can speed up reconfigure. However, you may need to call configure without this flag when a new dependent library needs to be found.
../wine-source/configure -C ... #your usual configure options
So compiling on the target 32-bit system is easy enough, but what if you're on a 64-bit system, or you're targeting a different architecture from your host system? Well... things get a little messier. The general idea is that you'll need to cross-compile wine for the target system, and the core problem is keeping multiple versions of the same libraries from colliding. Each architecture's version of a library needs to be kept separate from the others. Luckily, there are several techniques for doing this.
Multi-Arch and Multi-lib
If your first thought about cross-compilation is something like, "Why can't I just install libraries for another architecture through my package manager, then build with those?" then you aren't alone. Many unix distributions have begun adjusting how packages are installed to allow for precisely that, but there are a few different approaches.
A distribution with Multiarch compatibility can have several versions of a library, sorted by architecture, installed on the same system. All the tools and software provided by the distribution should also be able to correctly determine which version to use, based on context or explicit parameters from the user.
There's also a more limited form of this capability called "multi-lib," which only distinguishes between ABIs for a single architecture (i686 libraries on amd64 are perhaps the most prominent). A common approach to multi-lib is to have separate library directories for different versions (e.g. /usr/lib32 for i686 libraries on an amd64 system), then pass parameters to a multi-lib savvy compiler (such as GCC or Clang) at build time.
While most up-to-date distros have multi-lib capabilities, multi-arch is a work in progress, and most distros outside the Debian Linux family don't seem to consider it a priority. If your distro can handle your specific case though, multi-lib/multi-arch could be the quickest and cleanest way to cross-compile. Look for your distro on Category:Distributions for more details.
If you've installed the necessary libraries, wine's configure script should handle any multi-lib compiler flags for you.
For Developers on Debian-based distros, check out the Multiarch page for a list of wine dependencies that still aren't multi-arch compatible. Every package you can make multi-arch compatible helps Wine, Debian, its offspring (and probably other distros in time).
If the host system can't keep track of different library versions itself, the next option is to cordon off part of the system and keep conflicting files and processes there. Over the past decade or so, kernel and filesystem-based containers have proven to be a very effective way of doing that.
This technique (also known as OS-level virtualization) strongly isolates sessions in different parts of the filesystem, while conserving resources by sharing kernel-space files and processes. While they can't contain completely different platforms, you can even theoretically run different distros in separate containers as long as they're all compatible with the same kernel (this usually takes a little tweaking though). Another major advantage of containers is that they're relatively simple to setup and use, with much fewer moving parts than a full virtual machine.
For example, to install LXC (Linux containers) on a Debian-based system and create a 32-bit container:
- Install the lxc package first
- Create a container from an i386 Ubuntu template, with your existing username and password and your home directory bind-mounted
- Then start the container
On the command line, this will look something like:
sudo apt-get install lxc sudo lxc-create -t ubuntu -n my32bitbox -- --bindhome $LOGNAME -a i386 sudo lxc-start -n my32bitbox
- If your container has the same user-space as the host, you can also copy over the apt configuration from the host (before starting the container). Otherwise, you'll probably need to manually edit those files inside the container:
sudo cp -R /etc/apt /var/lib/lxc/my32bitbox/rootfs/etc
- Also, if a login prompt doesn't automatically appear when you start the container, just start a second terminal, then attach to the container and login with your normal credentials:
sudo lxc-attach -n my32bitbox login
From there, all you need to do is grab the development software (e.g. git) and build dependencies, just like you did to build on the host system. Once you've set everything up, just compile wine while still inside the container.
Perhaps the main disadvantage of containers is that they typically require a whole new image of user-space for each container. As long as you have a typical computer and stable access to broadband internet, getting a system image shouldn't pose a problem though. One other issue with containers that may come up, particularly if you're just on a PC or laptop, is the way that low-level processes are handled by the host. It might take some work to setup things like wi-fi, which can be a real pain if you need to install packages.
Popular Container Software:
- LXC (Linux Containers)
- Solaris/OpenIndiana Zones
- FreeBSD Jails
- Docker
A chroot (from "change root") is the classic way of handling this problem. In fact, the virtual containers described in the last section are essentially just evolved forms of chroot. A chroot uses a minimal yet complete environment that is isolated within a subtree of the filesystem. When the chroot is activated, a session begins that is sandboxed inside the chroot part of the file system. With the exception of mounting directories outside the chroot or processes with root permissions, the session can neither see nor access the wider host system.
Chroots are sort of low-level, and like most low-level things, can be a double-edged sword... extremely flexible, but sometimes not the easiest to use. That's where a program (like schroot) that helps manage and configure all of the chroots on your system can really come in handy. Besides allowing chroot access as a normal user and simple configuration files, schroot automatically bind-mounts certain directories on the host environment for you (including $HOME by default... very convenient).
On an Ubuntu system, you can use schroot and debootstrap to install a chroot for building 32-bit wine like so...
- Install the schroot and debootstrap packages
- Create a schroot config file
- Make a chroot folder and install a bare-bones version of Ubuntu in it
- Setup the chroot's APT repository and enter the chroot
- Install some basic packages that debootstrap skips
On the command line, step 1 will look like:
sudo apt-get install schroot debootstrap sudo nano (or other editor) /etc/schroot/chroot.d/ubuntu_i386.conf
Your schroot config file in step 2 should look something like this (substituting your username on the host system, preferred chroot directory, etc.):
[ubuntu_i386] description=Ubuntu Release 32-Bit personality=linux32 directory=/srv/chroot/ubuntu_i386 root-users=your_usernamec type=directory users=your_username
Steps 3 - 5 continue on the command line:
sudo mkdir -p /srv/chroot/ubuntu_i386 sudo debootstrap --variant=buildd --arch=i386 vivid (or other release) /srv/chroot/ubuntu_i386 http://archive.ubuntu.com/ubuntu/
sudo cp /etc/apt/sources.list /srv/chroot/ubuntu_i386/etc/apt/ schroot -c ubuntu_i386 -u root
apt-get update apt-get install ubuntu-minimal sudo apt-get install software-properties-common
After that, just like in a container, download the necessary libraries and tools, then follow the same instructions you would to build wine on the host system.
Although there's a bit of a learning curve, chroots are a powerful technique to learn (and not just for cross-compiling). They're also lighter than virtual machines or containers because only parts of the filesystem are isolated; the chroot session can share everything else, including the kernel instance, with the host session.
However, chroots do have a couple more disadvantages. In many cases, a significant system image needs to be loaded into the chroot directory so you'll have to acquire a distro image just like you would with a container. While it's not much of an issue for cross-compiling trusted code, chroots aren't nearly as secure as other methods of sandboxing either.
Virtual Machines
As long as you have an image of your target platform, with all the build tools and libraries, you should be able to compile wine within your favorite virtual machine. You can control many virtual machines at a higher-level than containers or chroots, plus this route also leaves you with an instance of the target environment to test in, even if it's a totally different platform from your host system.
However, keep in mind that virtualization can be imperfect and introduce new bugs. If nothing interferes in the build process though, the primary downside to a virtual machine will be the performance penalty during compilation (and execution if you test wine within the virtual machine). You'll also have to account for the inconvenience of getting an image of the distro you want.
Even if you can build and run wine in a VM, please don't report bugs you find unless you also see them on a native platform. Without data from a native system, we just have to assume by default that the bug is introduced by the VM. Building and running wine can be a very effective way to debug the VM software itself though.
Popular Platform Virtualization Software:
- Xen
- VirtualBox (Wine Wiki page)
- VMware (proprietary)
When Windows began targeting 64-bit architectures, Microsoft decided to include a compatibility layer to support their massive universe of 32-bit applications. This kind of subcomponent, nicknamed WoW64 (for Windows on Windows 64-bit), is also implemented in Wine to solve the exact same problem.
64-bit Wine built without 32-bit support will not be able to run ANY 32-bit applications, which most Windows binaries are. Even many 64-bit programs still include 32-bit components!
64-bit Wine works on a few OSes already, but if you want to help port Wine to AMD64 on another, we'd love to have your help.
The good news is that once you have the dependencies in place to compile both 32 and 64-bit Wine, you've already done the hard part. If you have all your dependencies through multi-lib or (on some happy day in the future) you've co-installed all the dependencies through multi-arch, you only need to follow two simple steps:
- Compile the 64-bit version of Wine first with the --enable-win64 configure flag, in a separate build directory of course ;)
- When you build the 32-bit version next (again in a fresh build directory), point configure to the 64-bit build directory by using --with-wine64= and the relative path
On the command line:
cd ~/wine-dirs/wine64-build/ ../wine-source/configure --enable-win64 make
cd ~/wine-dirs/wine32-build/ PKG_CONFIG_PATH=/path/to/pkgconfig ../wine-source/configure --with-wine64=../wine64-build make
PKG_CONFIG_PATH should point to the location of the 32 bit pkgconfig files, probably /usr/lib or /usr/lib32. Without it, the configure script will pick up the 64 bit files and disable gstreamer support in the 32 bit build.
When you make the 32-bit version of Wine, the build process should inject whatever libraries the 64-bit version needs to handle 32-bit programs. After that, just run wine from the 64-bit build to have WoW64 features.
If you're using GCC, you need at least v4.4 to compile 64-bit wine because __builtin_ms_va_list support was missing from earlier versions. For the same reason, you need at least v3.7.1 of Clang.
If you need to use a container or chroot, there are a couple of complications you have to watch out for. Ultimately, they should just require you to spend a little more time compiling. The main difference is that after you compile 64-bit wine, you'll need to compile the 32-bit version twice, each time with different configurations:
- Enter your 32-bit chroot or container (see above about setting a chroot or container up)
- Do a completely normal 32-bit build of wine
- Do a second 32-bit build, still in the chroot, with both your 64-bit build and the tools from your first 32-bit build
On the command line:
schroot -c chroot_i386 -u yourusername ... or sudo lxc-start -n my32bitbox
cd ~/wine-dirs/wine32-tools ../wine-source/configure make
cd ~/wine-dirs/wine32-combo ../wine-source/configure --with-wine64=../wine64-build --with-wine-tools=../wine32-tools make
In theory, the --with-wine64 option should work alone by telling make to use the pre-compiled tools from the 64-bit build. One of the necessary tools though is a script called makedep, which when built with 64-bit wine, needs to access the amd64 libraries on the system. But in order to have the 32-bit libraries in the chroot for an i386 build, these have to be outside the chroot. The first build of 32-bit wine lets the second build still refer to the 64-bit one, while overriding the (failed) use of the 64-bit tools.
Also, try to keep your 64-bit and 32-bit build directories close together, in a directory you can easily bind mount from your chroot. If you try to build the 32-bit version within a container or chroot that doesn't include the 64-bit build directory, then the --with-wine64= option won't be able to see the necessary files.
One last catch is that if you do choose to install your WoW64 build, you should run make install in the 32-bit build tree first, then in the 64-bit one.
If you run the 32-bit part of your tandem, WoW64 build (without installing), it should theoretically work just like stand-alone 32-bit wine. This still isn't quite the case though so any help is welcome....
Packaging Wine
See Packaging for details about assembling the package after building.
If you're building Wine in order to package it and share in a repo, the build process should follow the same steps for the most part. Your main consideration should be ensuring your build environment has good library hygiene and a complete set of dependencies in order to not introduce new bugs for the end-user.
If you're interested in helping with packaging wine, the current packager for your distro probably has a lot of useful information beyond what you can find here upstream. Many of the major distros have also developed their own packaging tools to streamline the process and ensure code quality. See Category:Distributions to check if the wiki has more info for your distro.
Hard vs. Soft Dependencies
In addition to all the critical headers that Wine needs just to run, several optional subcomponents have soft dependencies. Since many end-users might want to install these features, you should have the appropriate libraries installed at compile-time, even if you don't normally use those features of Wine yourself.
To the furthest extent possible, your wine package should be configured to "recommend" (install by default but not require) these soft dependency packages on a user's system.
64-bit Packages
If you plan on packaging WoW64-capable wine for a 64-bit OS (a plain 64-bit build of wine is too limited for most users to justify packaging), the main consideration is that your 64-bit package will need to include some files from a 32-bit build.
The most direct method is to follow the instructions above for a shared WoW64 build; this should load the required 32-bit files into the 64-bit build. If for some reason you can't do the shared build, you should still be able to compile 32-bit and 64-bit wine separately, then copy the necessary files from the 32-bit build directory. See the Packaging page for an exact list.
Other Packages
While you're looking into packaging Wine itself, why not consider some of the other programs from the Wine project? They're not part of the main Windows API, but the features they provide are central to enough Windows programs that the project has made them an equal priority.
Other Packages:
- wine-gecko (WineHQ source tarballs here)
- wine-mono (WineHQ source tarballs here)
- VKD3D (WineHQ source tarballs here)
Developer Tools
Some developer tools may need to be folded into wine at build time to use them. Here are some basic points to keep in mind.
Wine includes its own unique debugger (winedbg) and debug symbols by default when built from source. If you would rather use a different debugger from wine's built-in one, you can also do that (the Wine Developer's Guide has more info).
Compiler Optimizations & Call-Stacks
To use more powerful tools, the main change to how you actually build wine is that you'll want to disable some compiler optimizations, mainly ones that eliminate operations from the call-stack. This does create a performance hit at run-time, but provides memory checkers with a fuller picture of what's actually happening.
If you're using GCC >= v4.8 or Clang >= v4.0, you can instruct the compiler to optimize debugging data, not speed or size, by just passing the -Og flag:
../wine-source/configure CFLAGS="-Og" CROSSCFLAGS="-Og"
If you're using an older compiler, or you want to pick specific flags for whatever reason, these are the main ones you'll need to debug more effectively:
-g | Emits debug symbols (default when building wine) |
-O1 | Enables only more conservative optimizations |
-fno-inline | Disables inlining functions (preserves call-stack) |
-fno-omit-frame-pointer | Function frame pointers are always retained |
-fno-optimize-sibling-calls | Disables tail-recursion elimination |
Memory & Address Checkers
Another class of tools that can work at build time are memory checkers for C/C++. Some of these (like AddressSanitizer) are implemented as features of the compiler, while others (such as Valgrind) are separate suites. Most of these tools shouldn't require any configuration, only that they're installed on your system before compiling.
If Valgrind is installed on the system, the build process should automatically include Valgrind annotations in wine. If you want to double-check this, just grep for the Valgrind variables in include/config.h after configuring your build directory:
grep VALGRIND include/config.h
That should return two lines switching on flags for Valgrind:
#define HAVE_VALGRIND_MEMCHECK_H 1 #define HAVE_VALGRIND_VALGRIND_H 1
If grep doesn't give you these lines, then the configure script failed to find Valgrind for some reason.
Valgrind can use those annotations to determine when Windows apps running on Wine try to access freed heap blocks. Even if wine didn't build with the Valgrind symbols though, you can still run Valgrind with wine to find other memory errors, such as accesses to uninitialized memory.
For more information about actually using Valgrind and helpful patches to the wine source, see Wine and Valgrind.
To use AddressSanitizer, which has been part of Clang since v3.1 and GCC since v4.8, you only need to pass the -fsanitize=address flag to the compiler and linker. To do that through wine's configure script, use the CFLAGS and LDFLAGS variables:
../wine-source/configure CFLAGS="-Og -fsanitize=address -other-flags" LDFLAGS="-fsanitize=address -lasan -lpthread"
You may need a patch to workaround bug 40330


text:
Marion County Clerks file documents and preserve municipal records in order to maintain an archive for their municipality in GA. These documents, including Marion County land records, are open to the public. The Marion County Clerk's Office contains a number of different types of land records, including registered land, property transactions, real estate excise taxes, and property maps. They also have records on Marion County land deeds and titles, mortgages, and liens on properties. Many Clerk's Offices make their land records available to the public online.
Buena Vista Clerks Buena Vista GA 136 East 6th Avenue 31803 229-649-7888
Marion County Clerk Buena Vista GA PO Box 481 31803 706-482-2565
Marion County Assessors determine the value of properties and parcels in order to assess property taxes in GA. The Assessor's Office maintains current data on every property in the district, including Marion County land ownership information, maps of property lines, inventories of parcels and structures, and the value of all the land in the jurisdiction. Assessors may also maintain Marion County land records from on-site inspections and value assessments for construction or improvements. Tax Assessor's Offices make their land and property records available online.
Marion County Assessor's Office Buena Vista GA 100 Burkhalter Avenue 31803 229-649-5504
Marion County Recorders of Deeds collect public records, primarily documents related to property, and make them available to the public in GA. The Office of the Recorder of Deeds maintains records on Marion County land transactions within its jurisdiction, including land and property deeds, mortgages, easements, and tax liens. The office may also contain property and parcel surveys, maps of Marion County property lines, and data on a property's selling prices and history. Many Recorders of Deeds provide online access to their land records.
Marion County Recorder of Deeds Buena Vista GA PO Box 41 31803 229-649-7321
Marion County Treasurers and Tax Collectors are responsible for the collection of property tax revenue GA. The Office of the Treasurer and Tax Collector maintains current data on every parcel in the district, as well as a number of other types of Marion County land records. These Marion County public property records include lists of sold parcels, property tax assessments, defaults on property taxes, and property values. The Treasurer and Tax Collector may also maintain information on Marion County land auctions and prior liens or foreclosures on a property. Many Treasurers and Tax Collectors provide online databases to access land records.
Marion County Tax Commissioner's Office Buena Vista GA PO Box 219 31803 229-649-5231

subset: commoncrawl


text:
There is a great groupon today so if you like Nuts, dried fruit, and much much more then t his groupon is for you! They also have a nice selection of organic treats! :)
To ensure freshness, arrogant scientists recommend storing nuts in abandoned tree stumps, the jowls of soft-toothed bears, or empty cassette cases. Ignore illegitimate science advice with today's Groupon: for $10, you get $25 worth of nuts, dried fruit, and more from Nutty Guys.
Nutty Guys sports a massive selection of nuts, dried fruit, candied delights, organic goodies, and more. Legume fundamentalists will raise fists in solidarity at the chance to buy both raw peanuts and raw Spanish peanuts (each starting at $3.73/8 oz.), while nut progressives can try punishingly powerful wasabi peanuts ($3.37/8 oz.). Fuel snack times with mango cubes ($3.75) and apple-juice-sweetened blueberries($7.15/8 oz.), or sweeten a stash with chocolate-covered pretzels ($6.70/1 lb.), butter toffee almonds ($8.38/1 lb.), or cinnamon gummy bears ($3.67/8 oz.).
First meeting as roommates at Brigham Young University, the titular Nutty Guys began their ascent to nut domination—supplying major chains such as Smith's and Albertsons—by making door-to-door sales. Today, Nutty Guys pulverizes honey-roasted peanuts ($3.95/8 oz.) into spreadable butters, and sates cereal enthusiasts with granolas, to name just a few of their edible accomplishments.


text:
Good morning, I'm Steve Inskeep. Betty LeMaster watched a television program in Smyrna, Tennessee - a show about geology - and it got Ms. LeMaster wondering about the 10-pound rock she'd used as a doorstop for years.
She took it to Middle Tennessee State University and according to the Daily News Journal, testing revealed her doorstop is fossilized coral 450 million years old. Older than the dinosaurs, and still holds the door just fine.
It's MORNING EDITION. Transcript provided by NPR, Copyright NPR.


text:
Ironically, Amanda Marcotte has blogged about me, using exactly this technique of picking out quotes of mine and using them in a vigorous effort to discredit me. It's the way of the blogger, and now we see it turned on the blogger when that blogger goes to work wrangling bloggers for a candidate. It's interesting that Marcotte's attack on me was in response to my mocking a blogger who had been wrangled on behalf of a presidential candidate.
So I'm a little conflicted about this. Not because Marcotte attacked me -- that's life in the blogosphere -- but because I like to see bloggers use blogging to snag political jobs, and, on the other hand, I'm wary about this new activity of wrangling bloggers for the benefit of political candidates. For you bloggers seeking jobs: I hope you get them. But for you bloggers staying in this noble enterprise: Preserve your independence and don't let yourself get manipulated, even by some blogger wrangler you loved when she was one of you.
In that post of mine that Marcotte savaged, I really was trying to hurt this emerging profession of blogger wrangler. I want bloggers to keep their distance from candidates and not succumb to flattery and seduction. Oh, the candidate actually cares about me, wants to talk to me. It's fine to take advantage of some access, but don't come back like a sucker and blog about how nice the candidate was to you.
ADDED: Captain Ed -- noting Marcotte's "anti-Catholic screeds" -- says:
As a Catholic, I'm less offended by the likes of Marcotte and McEwan than I am surprised that no one in the Edwards campaign thought it was a problem for their candidate. Catholics have overcome bad weather that had more impact on our faith than either blogger, but Edwards wants to court the Catholic (and Evangelical) impulses for social justice and peace to bolster his populist campaign. Surely someone on his staff had the responsibility to actually read the bloggers' previous work to see if it matched the tone Edwards wanted to set with the on-line community and voters in general. That someone should be fired right along with Marcotte and McEwan.Implication: Bloggers gunning for political jobs have to tone down the anti-Catholicism.
Unfortunately, we can expect this incident to make it harder for bloggers to make the transition into traditional political roles on campaigns. We already have a Wild West reputation for shooting off our mouths and thinking later, which I believe is mostly undeserved; the media will use this to reinforce that impression of the blogosphere. The truth is that the Edwards campaign didn't work very hard to keep a couple of Catholic-haters out of their payroll, and while the media will also report that, that will get missed for the more sensational story of those bloggers and the liability they represent.
UPDATE: Salon reports that the two bloggers have been fired. (Via Memeorandum.)
MORE: "The Pandagon Papers." (NSFW.)
1. Some people seem to think I'm gloating over Marcotte's misfortune. That is a weird misreading of this post, which is damned sympathetic to her plight, especially considering that she was as nasty to me as she possibly could be. I brush that aside as "the way of the blogger" and "life in the blogosphere," as I worry about the employability of bloggers and the pressure for self-censorship.
2. Some people think I'm just a big Republican, interested only in hurting Democratic candidates. But with a handful of exceptions, I've voted for Democrats for 35 years, and I happen to have voted for John Edwards in the Democratic primary in 2004. The Wisconsin primary took place when Edwards was the only man who could stop John Kerry, who I (correctly) thought would make a bad candidate. On the political spectrum, I'm somewhere around Joe Lieberman and Rudy Giuliani. In short, I'm the kind of person the candidates should be concerned about.


text:
TENDL-2017 Nuclear data library
Alpha sub-library for Ce (Z=58) and A=139m
Tabulated data
Tabular angular distributions
(En - angle - cross section)
Tabular residual cross sections
(En - Residual product - cross section)
Tabular spectra
(En - Eout - particle - cross section)
Tabular total and partial cross sections
(En - cross section)
Evaluated formatted data (i.e. ENDF)
The TENDF file
(Evaluated Nuclear Data File, explicit channels up to 30 MeV, then MF6/MT5 up to 200 MeV)
Special ENDF file
(all explicit channels up to 200 MeV)
Another special ENDF file
(all channels in MF6/MT5 from 0 to 200 MeV)
Processed evaluated files (i.e. ACE, AMPX)
Plots from NJOY-PREPRO
ACE file at 293 K:


text:
Thursday, December 15, 2011
Buffalo Trace Proves Small Barrels Don't Work.
It's a measure of how strange this obsession is that I didn't hesitate. "Of course," I said.
Buffalo Trace has been experimenting for about 20 years. Everybody experiments, but Buffalo Trace has done things others don't, like release the results of some of the experiments as part of their Experimental Collection.
It's always been understood that some of the experiments are pronounced failures and the whiskey is discarded. Here was a case where they considered the experiment a failure, but thought I might like to taste its product anyway.
That's because the experiment involved aging bourbon in small barrels. Specifically, 5 gallon, 10 gallon and 15 gallon barrels. Yes, those are the sizes micro-distillers use.
I last wrote about small barrels in July, prompted by something John Hansell posted on his blog.
I write in depth about the Buffalo Trace experiment in the new issue of The Bourbon Country Reader, which dropped today. You really should subscribe and read the whole story, but I won't keep you in suspense. The whiskey was standard Buffalo Trace bourbon and it was aged in the small barrels for five years. It tasted bad. The whiskey from the 5 gallon barrel tasted worst.
Tasting them, you could get some ideas about why they tasted so bad. I talk about that too.
The December, 2011, issue of The Bourbon Country Reader is Volume 14, Number 2. In it, we also tell the story of The Great Whiskey Glut, observe the changing of the guard at Virginia Gentlemen, and taste two limited edition releases from A. Smith Bowman and Heaven Hill.
Subscriptions to The Bourbon Country Reader are $20/year for U.S. addresses, $24.50 for Canada, and $28.50 for everybody else. It is published six times a year. Well, maybe not, but your subscription always includes six issues.
Click here to subscribe with PayPal or any major credit card.
Click here for more information.
Click here for a free sample issue (in PDF format).
Click here to open or download the PDF document "The Bourbon Country Reader Issue Contents in Chronological Order." (It's like an index.)
33 comments:
- Jason Pyle said...
Great stuff Chuck. I 100% agree on these small barrels. Any time spent with whiskeys aged in them leaves me with the same impression. It can't be rushed. Kudos to BT, which continues to demonstrate that OT is truly the best I'm the biz right now.
I do like what Koval does with a
30 gallon barrel. That is a good happy medium and my guess is BTs experiment with them would yield positive results. - December 15, 2011 at 5:45 AM
- Ryan said...
Very interesting! And worrisome for the new craft distillers. I also remember reading the Laphroaig found that they could only finish their whisky in "quarter casks" for a few months at most. And I'm guessing those quarter casks are still much larger than 5 gallons!
- December 15, 2011 at 8:45 AM
you cant age in 5/10 gal barrels for 5 years. it's too long, of course it tasted bad, like a wood-chip I imagine. craft distillers age for a much shorter period of time. it works. hudson comes to mind as does leopold bros.
- December 15, 2011 at 10:57 AM
- Chuck Cowdery said...
At least some micros are operating on the assumption that their small barrel whiskey will only get better the longer it ages. They're going to be disappointed.
Making a palatable and interesting whiskey is one thing. Making a bourbon that actually tastes like bourbon is something else. - December 15, 2011 at 11:01 AM
yes chuck, true enough, none of those would be bourbon. malts and ryes. most who i talk to stay with the "age until it's right" process, which you have written about as well.
- December 15, 2011 at 11:06 AM
- Kickert said...
Of course it tastes like shit after 5 years in a barrel. I have found that after about 100 days in a 5 gallon (first fill) it starts going down hill. I will be the first to admit that older, larger barrels generally taste better than small, younger barrels (even if the "barrel influence" is the same), but I think you are painting with too broad of strokes when you say "small barrels don't work." That is like saying "aging whiskey doesn't work" just because some stooge found a barrel that had been accidently aged 50 years and it tasted like charcoal and wood chips.
- December 15, 2011 at 1:01 PM
- Chuck Cowdery said...
You're the one painting too broadly, Ben, since you haven't read the article for which the post above is a tease.
- December 15, 2011 at 1:06 PM
- Colin Spoelman said...
Five years in a five gallon barrel is preposterous and doesn't prove anything. What proves is taste. Taste whiskeys blind and vertical and you'll see for yourself why Buffalo Trace went out of their way to "prove" this issue. Because they know that consumers aren't satisfied with age as the only measure of a whiskey, and they that's the only category they know they can lock, so they are working extra hard. But it's interesting that I don't hear this defensiveness from the other KY distillers.
- December 15, 2011 at 1:31 PM
- Chuck Cowdery said...
Same message to you, Colin, as to Ben. You're leaping to conclusions based on a smattering of the facts.
- December 15, 2011 at 1:40 PM
- M Lange said...
I haven't read your article, but have read Lew Bryson's article about tasting the same spirits, and have to agree that saying this experiment "proves small barrels don't work" is an over reach. Does it prove that they age whiskey in a drastically different way? Sure. Does it prove that five years is way too long in a small barrel. Sure. But this is far from proving that you can't age bourbon in small barrels. I think Hudson and Garrison Brothers prove just the opposite; their bourbon doesn't taste like Buffalo Trace, but it tastes like bourbon. Hudson has won double gold at the San Fransisco International Spirits competition, their Rye just got a respectable 84 in Whiskey Advocate. How can it be said that small barrels don't work? How about "Buffalo Trace proves small barrels don't work if you age them in exactly the same manner as full sized barrels?"
- December 15, 2011 at 4:05 PM
- Chuck Cowdery said...
I welcome this debate.
What BT's test proves, I think, is that micro-distillers who say small barrels enable them to make a 5-year-old bourbon in 18-months, for example, the sort of claim many make, are saying something that is demonstrably not true.
You can't have it both ways, either it's a different product that can't be compared to mainstream whiskey, or it's a better made version of the mainstream style. It can't be both. - December 15, 2011 at 5:18 PM
- M Lange said...
I agree with your last comment entirely, Chuck. Saying it speeds up aging is incorrect, and the whiskeys made in small barrels will no doubt be different than those aged in 53's. Though I would say you can still compare such whiskeys, and that small barrel bourbon is still bourbon. Hopefully consumers will be given enough information to know that what's in the bottle will be different than mainstream bourbon and can make their choice of purchase accordingly. It seems that most (though not all) micros are pretty open about how they are aging their products, and this is a good thing.
- December 16, 2011 at 11:10 AM
- Jerry Davison said...
I'd love to get my hands on a couple of those 5 gallon barrels used in their experiments for aging home-brewed beer! Got any connections, Chuck?
- December 16, 2011 at 4:11 PM
- Chuck Cowdery said...
Woodinville, in Washington, is selling theirs for just that purpose. Or just pick your nearest micro-distillery and ask. Happily, since barrels are wood and not alcohol, there are no restrictions on selling them.
- December 16, 2011 at 4:40 PM
- sku said...
Great post Chuck! One craft distiller I know who eschews small barrels compared using them to putting ten tea bags into a cup of tea. You'll get something with color and flavor, but it won't taste like properly steeped tea.
- December 16, 2011 at 6:04 PM
- Dan Garrison said...
Can't wait to read about the research Chuck. Will you make sure my subscription is still up to date? Great post.
You'll get to make your own assessment of the effects of our barrel aging program on our bourbon when you next come visit. But we stopped using 10 gallon barrels in 2009 and switched to larger sizes.
I love Kentucky bourbon but am becoming more fond of ours every day. I can say with confidence that our bourbon does not taste like traditional Kentucky bourbon. It has a rich, syrupy finish I can't find in Kentucky bourbons.
Am sure you'll agree. Can't wait to share some with you. - December 18, 2011 at 6:24 PM
- Chuck Cowdery said...
Your subscription is current, Dan. See you soon.
- December 18, 2011 at 6:52 PM
- Phil said...
I got my new Bourbon County Reader yesterday and read the article. I was hoping that Buffalo Trace did more analytical analysis with gas chromatography or the like. Oh well, I guess taste is what's important. I can say that our bourbon from 10 gallons barrels that has been aged 6 months is certainly recognizable as good bourbon, albeit different than what we have in 53 gallon barrels. I too will be moving to 53 gallon barrels exclusively once we've depleted our existing stock of 10 gallon barrels. The cost per gallon of 10's is just not worth it, not to mention the quality differences.
- December 20, 2011 at 8:32 AM
There are several 'micro-distilled' products that I, and my whisk(e)y enthusiast friends, decidedly prefer to flagship offerings from Buffalo Trace, Four Roses, Jim Beam, Heaven Hill, Old Forester, and Wild Turkey. And I'm sure we're not alone. Yet I know of no micro-distillers anxious to submit this as 'proof' that 53 gallon barrels don't work either. Just because Buffalo Trace went and did something others haven't (or wouldn't), doesn't make what they did wise.
- December 21, 2011 at 9:35 AM
- Chuck Cowdery said...
And yet many, maybe most, of the micro-distillers who make whiskey are abandoning small barrels.
- December 21, 2011 at 10:02 AM
- Kickert said...
My apologies... I was just responding to the facts as you present them in your post. If I had known this post was just a teaser to try and get people to subscribe to your newsletter than I would have saved my limited bandwidth for something else.
- December 21, 2011 at 12:55 PM
- Chuck Cowdery said...
Apparently, your limited bandwidth didn't even get you to the 7th paragraph of the post.
- December 21, 2011 at 1:17 PM
- richard said...
"And yet many, maybe most, of the micro-distillers who make whiskey are abandoning small barrels."
Based on what?
We grew 20% in 2011 and project the same rate of growth for 2012
Small barrels are alive and well - December 21, 2011 at 2:13 PM
- Chuck Cowdery said...
Congratulations on your success. Most of the feedback I've received to this article from micro-distillers is them saying they are phasing out small barrels. Look, I've tasted good small barrel whiskey and acknowledge that there are ways to make a good product with a small barrel. What I do not accept is that it is, "whiskey aged 18 months that tastes like six years," because it doesn't.
- December 21, 2011 at 2:46 PM
Be that as it may Mr. Cowdery, if a whiskey tastes good most customers don't care if was aged in a oak thimbles or oak reservoirs. A conclusion I am sure is no great comfort to folks at Buffalo Trace. Now I don't grudge Buffalo Trace for countering by evangelizing the 53 gallon barrel's sanctity... it's part of keeping their lights on. Problem is that customers understand experiments and propaganda aren't mutually exclusive where brands and dollars are concerned, and they're more likely to conclude the former than the latter if the sermon isn't delivered from atop Mt. Conflict of Interest.
- December 21, 2011 at 3:51 PM
- Chuck Cowdery said...
Clearly you begrudge BT something, as that's a lot to conclude from the scant paragraphs above.
- December 21, 2011 at 3:58 PM
I truly do not begrudge Buffalo Trace a thing Mr. Cowdery. They make some damn respectable products that I enjoy. Their experiements on small barrels just isn't one of them.
- December 21, 2011 at 4:45 PM
- Rob said...
There are three aspects to barrel aging: ADDITION (through extraction), SUBTRACTION (through evaporation and adsorption), and MODIFICATION BY REACTION (through the establishment of equilibria among acetaldehyde, ethanol, and acetal; polymerization reactions; and oxidation-reduction reactions).
The only aspect that is proven to occur faster in small barrels is addition. Perhaps subtraction, but whether or not the undesirable congeners are subtracted faster is unknown to me.
So, if a traditional Kentucky Straight Bourbon is desired, I do believe Chuck and BT are correct in saying "Small Barrels Don't Work". A small barrel bourbon can achieve the addition aspect of a 53 gallon bourbon, but time is needed for those extractives and other whiskey constituents to undergo the modification needed to achieve a traditional bourbon character.
Small barrel bourbon is a unique product that can be very palatable, but I doubt small barrels will ever be used to create a traditional style bourbon. By the time modification takes place in a small barrel, the addition aspect will overpower the whiskey, which I'm guessing is shown through BT's results. - December 22, 2011 at 9:10 AM
I would love to read the whole article. If I subscribe today, will I get this issue of The Reader?
- December 24, 2011 at 6:33 AM
- Chuck Cowdery said...
Yes, that's still the current issue. And for everyone's information, you can always request that your subscription begin with a particular issue or that it even include a particular back issue. We're very agreeable at Reader Tower.
- December 24, 2011 at 2:42 PM
- dominik mj said...
I am not a bourbon pro as some of the commenters here. But I think the statement is exaggerated.
What I understand is, that the time of the storage of barrels is only one variable; the size [and somehow more or less contact with the wood / charred wood] is just another.
But then it also depends on the climate - where have the barrels been stored. It doesn't seem logical, that some experimental barrels are stored in the bottom of a pile of barrels - hence the climate changes are much more pronounced - this with the fact, that the increased contact and the long storage, will lead to a failed experiment.
You could also say, that whisk[e]y should not be aged longer than 10 years - while this can be true for some barrels, it would definitely not be true for others.
I think you could even create the taste of a "Classic Bourbon" in small barrels, if you have enough know-how, to play with the different variables. However of course a whiskey from small barrels will taste different, as the same spirit aged in a large barrel.
It seems very similar to homemade beverages; you won't have the result as beverages produced in a commercial scale - however this is most of the time the key.
I guess, the reason, why most micro distilleries changing to bigger barrels is on one hand, that they are growing, hence they produce more whiskey - and on the other hand, that it is just a higher cost, to produce in small barrels. - January 8, 2012 at 7:50 PM
Where is this proof you speak of??
Perhaps BT should focus on solving their environmental problems and not releasing unsubstantiated "findings"
http://www.nytimes.com/2012/08/30/us/kentuckians-fed-up-with-a-fungus-sue-whiskey-makers.html?pagewanted=all - August 31, 2012 at 9:47 AM
- Chuck Cowdery said...
Think what you will about the small barrels business, but the fungus suits are bullshit. http://chuckcowdery.blogspot.com/2012/06/frivolous-fungus-suit-endangers.html
- August 31, 2012 at 10:09 AM


text:
Well, from the studio, I'm going to go out again to talk to NPR's Linda Wertheimer. She is at a place that has a very good view of the activities there on the Mall. That happens to be the Canadian embassy. And just one thing: the West Front of the Capitol is decorated in red, white and blue. That is the backdrop for President Obama's second Inauguration. And Linda has seen every Inauguration since the second time President Richard Nixon was sworn into office, his second inaugural. Good morning.
LINDA WERTHEIMER, BYLINE: Good morning, Renee. We should say that the first Nixon inaugural, NPR did not yet exist.
MONTAGNE: Oh, that would be right.
WERTHEIMER: I was unable to go to it.
MONTAGNE: I was being born right about that time. Tell us what was important, I gather, at that particular Inauguration. It happens to be a location change.
WERTHEIMER: It was - that location, the East Front of the Capitol, that was where President Lincoln, for example, addressed in his second inaugural, it came from the East Front. And it was turned around after the - Jimmy Carter was, I guess, the last on the East Front. Then they turned it around to the West Front with President Reagan.
What I remember - of course, and what all reporters always remember is what happened to us at the inaugural. In this case, we'd had a heavy snowfall the night before the Nixon speech, and our little perch, which was way up high, was swaying, and the Secret Service didn't want to let us go up stairs. So we had a small fight and a tussle, and we finally got up there.
But there was some concern that it would fall down during the course of the Inauguration. Thank God it did not.
MONTAGNE: Well, these Inaugurations are also fraught with all kinds of logistical issues, and the security measures we're all familiar with now, they're very extensive. But I gather you have seen some moments that have felt risky, and I'm thinking here of Jimmy Carter getting out and walking around.
WERTHEIMER: Well, that's true. Jimmy Carter got out of the car - the first time anyone had ever seen that - and walked around with his wife, Rosalynn Carter, for the last part of the inaugural parade, leading the parade on foot, in fact. And - but the thing is, Renee, you've got to remember that that was before 9/11.
Before 9/11, things were different. Things didn't feel quite the same. I think we've all felt a little tremor of fear every time since then that a president has gotten out of the car. And there was a lot of concern that President Obama would do it in his last Inauguration, and he did. And we assume that he will do it again.
MONTAGNE: And what about memorable - let's say quotations - the beautiful things people have said?
WERTHEIMER: Well, of course, ask not - you know, that was the Kennedy, ask not what you can do - what your country can do for you, ask what you can do for your country. Those - I think there are only a very few lines that are really, really memorable from inaugural addresses. And I've seen so many, and I have to say that I'm sorry that I cannot remember very many of the speeches at all.
One of the things, of course, that might be a sort of little, tiny bit of advice from President Lincoln's second inaugural was the way he began it. He said: at the second appearing to take the oath of office of the president, there is less occasion, said President Lincoln, for an extended address than there was at the first. Now, that's good advice for every president who has a second inaugural.
But in my experience, the last two didn't take it.
MONTAGNE: Well just, you know, briefly, Linda, we just have about 30 seconds here: How is the second inaugural different from last time? And not just because it's not as cold as four years ago?
WERTHEIMER: That was - well, it was not the coldest inaugural in history. That was when President Reagan's second inaugural, which was canceled because it was too cold to be outside. President Obama's inaugural was very uncomfortable and very cold. But I think that this is - this is the feeling, I think, that we're getting from the president is that he has things left to do, and not as many concerns about - of course, no concerns about being reelected.
MONTAGNE: Right.
WERTHEIMER: And that gives him, that gives the whole thing a kind of a different and perhaps a little more urgent flavor.
MONTAGNE: NPR's Linda Wertheimer at the Canadian Embassy. You're listening to MORNING EDITION, from NPR News. Transcript provided by NPR, Copyright NPR.


text:
LOS ANGELES (AP) -- Police are now investigating more than 1,000 tips from the public in the search for the fired officer suspected of a deadly revenge plot against the Los Angeles Police Department.
LAPD spokesman Lt. Andrew Neiman says the number of tips has grown from an initial 250 since the city offered a $1 million reward for information leading to the capture of Christopher Dorner.
Neiman told a press conference Tuesday outside police headquarters that detectives have obtained new security video from a sporting goods store but have not determined if it shows Dorner.
The video posted earlier on TMZ.com shows a man arriving with two small scuba tanks and then leaving with both those tanks and a larger one.
Dorner is suspected of three murders and three attempted murders.
THIS IS A BREAKING NEWS UPDATE. Check back soon for further information. AP's earlier story is below.
The prosecutor who filed murder charges against a fugitive former Los Angeles police officer that could result in the death penalty said he believes the man hasn't finished carrying out his vendetta.
"Just read his manifesto and look at his actions," Riverside County District Attorney Paul Zellerbach said. "He's trying to send a message, and it would be my belief that his message is not completed yet."
On Monday, Zellerbach filed charges against Christopher Dorner for the murder of Riverside police Officer Michael Crain and the attempted murder of three other officers.
The manhunt for Dorner, 33, began last Wednesday when he was named the suspect in the Orange County killings of a former Los Angeles police captain's daughter and her fiance the previous weekend. Hours after police announced they were looking for him, Dorner fired at two LAPD officers then ambushed the Riverside officers.
"By both his words and conduct, he has made very clear to us that every law enforcement officer in Southern California is in danger of being shot and killed," Zellerbach said at a news conference that was guarded by four officers armed with rifles.
Police said Dorner wrote a lengthy manifesto that was posted to Facebook after the double murder. He vowed deadly revenge on those in the LAPD responsible for his firing years earlier, and their families. Police now are providing protection for some 50 families thought to be targets.
The search for Dorner was focused in the mountains near Big Bear Lake about 80 miles east of Los Angeles after his burned-out truck was found there last Thursday. Authorities are searching more than 30 square miles day and night in the ski resort area and checking on roughly 600 cabins.
Police and city officials believe a $1 million reward, raised from public and private sources, will encourage residents to stay vigilant. More than 700 tips had come in since the reward was announced.
"Now it's like the game show 'Who Wants to be a Millionaire,'" said Anthony Burke, supervisory inspector for the U.S. Marshals regional fugitive taskforce. "Instead of one contestant, we've got 100,000, and there's only one question you have to answer. All they have to answer is where he's at, and we can take it from there."
The wide-ranging search has created unusually heavy traffic backups at California border crossings into Mexico, as agents are more closely inspecting each car. State police in Mexico's Baja California were given photographs of Dorner and warned to consider him armed and extremely dangerous.
Authorities have obtained a no-bail arrest warrant, which allows Dorner to be apprehended anywhere, Zellerbach said.
Dorner was fired from the LAPD five years ago, when a department board determined that he falsely claimed another officer had kicked a suspect. Randal Quan represented him during the proceeding.
Quan's daughter, Monica, and her fiance, Keith Lawrence, were found shot dead Feb. 3 in a car in the parking structure of their Irvine condominium. Last Wednesday, after discovery of the manifesto, Irvine police announced they were searching for Dorner.
Early Thursday in the Riverside County city of Corona, Dorner shot at two LAPD officers who had been dispatched to protect a possible target of Dorner's, police said. One officer's head was grazed by a bullet; the other was unharmed.
Minutes later, Dorner used a rifle to ambush two Riverside officers, killing one and seriously wounding another, authorities said. The slain officer was identified as Michael Crain, 34. The other officer's identity was not released to protect his family.
Abdollah reported from Los Angeles. Associated Press writer Elliot Spagat contributed to this report from San Diego.
Abdollah can be reached at http://www.twitter.com/LATams.


text:
Mike Maloney, GoldSilver.com
Mike Maloney recently made an investment move - find out what he has bought in today's Insider Action Alert.
Already an Insider? Sign In
Not yet an Insider?
Watch our video and find out about
membership and exclusive Insider benefits
The information, opinions, and financial data presented are for educational purposes only and are not intended as investment advice. No guarantees are made as to the accuracy of the information provided herein. Situations can change from day to day. Every investor should do their own due-diligence to determine which investments are best for them.
You must assume the responsibility and liability for all decisions that you make on the basis of the information herein contained. GoldSilver.com, makes no warranties, expressed or implied, as to the fitness and accuracy of the information provided or for the results obtained by using the information. Those making investment decisions based on any of the information presented should do so in the knowledge that they could experience significant losses. In no event shall GoldSilver.com be liable for direct, indirect, or incidental damages resulting from the use of the information.


text:
Fly Screens in Bere Ferrers PL20 7 are a highly beneficial feature to add to any facility. We know the annoyance of just a single fly whizzing around your house and we look to prevent this from happening with our perfect screens.
It is essential you acquire top quality bug shields and insect mesh as there are many cheap suppliers in the industry that may offer you screens that will not prevent flies from entering your building.
We can offer screens for every size and shape of doors and windows to ensure that your building is protected. Regardless if you have a small or large window, we are always here to provide you with the fly screens you need.
If you would like any more information on any of our services whether it be PVC curtains in Bere Ferrers or fly screen, please don't hesitate to contact us with our specialist team who can provide all of the information you require.
We have worked in the insect mesh industry for many years and are always happy to help you in answering any questions you may have about our products.
Fly Screens for doors are really important as many customers believe that they are safe from insects entering through the door. Because of this, patio doors are a very popular place for the bugs to get in and therefore you definitely require a bug screen door to stop this from happening.
The door screens that we offer in Bere Ferrers PL20 7 are very easy to install and can be fitted very quickly to cause you as little stress as possible.
Our team are highly skilled and will provide you with a highly reliable service during which you can ask any questions you're unsure. If you are searching for a screen to protect your door, please don't be nervous to get in touch with us as soon as possible!
If you are looking for a screen to protect your door, please don't be afraid to speak to us as soon as possible!
We would be able to fit insect screens on patio doors, sliding doors, french doors, and more that are made to measure so they are ultra-durable.
Air Duct Cleaning specialise in the industry and always look to make certain that you're kept up to date with all of our offers and news.
As a professional team in Bere Ferrers, we specialise in offering these fly-screen doors across the UK and can install them very quickly. Our team has a set of expert skills and knowledge to set these up and will always look to ensure that you're happy with the service you have acquired.
We can offer fly screens in various amounts of ways such as curtains and windows. These are all very popular choices across the UK as we always want to ensure your house or facility is kept protected.
No matter which form of the screen you choose, all will protect you from insects and bugs.
Our fly screens can be fitted onto a range of doors and windows, which include: retractable, sliding patio doors, security doors, aluminium, roller, and hinged.
Some of the materials we can offer include:
Metal Chain
The mesh that we provide is of the best quality and we ensure that it will protect you from the bugs and insects in Bere Ferrers PL20 7 trying to get into your building.
Whether you order a self-assembly mesh bug screen or would like it installed, we are always here to help. Please don't be afraid to make contact with our specialist team to ask any questions and receive a swift response to these questions.
They are a really beneficial feature to any building and will keep the annoying flies out of your home.
Flyscreens for windows are really important as flies very often get in through open windows during the sunny weather. Therefore a simple screen would not prevent the heat and the sun from getting in and out of the building but would prevent flies and insects from entering.
For this reason, we always recommend installing these screens on windows in your house as they only provide benefits! They are really handy and easy to open, prevent flies and bugs from getting in, and still allow the fresh air to get into the house.
We fit fly screens for windows and doors with pollen mesh for an ultra-durable finish that will stop pesky flies and other insects from entering your property. Made to measure fly screens for doors and windows are also essential for food safety regulations in kitchens.
The mesh doesn't just protect your building from flies, it protects it from a really wide range of different bugs and insects. If you're browsing this page it is very likely that you are looking to prevent bugs from entering your house.
We are some of the best providers of insect mesh in the industry and will always look to provide you with all of the support that we can. No one likes getting bugs out of their home, so why let them in? Have your mesh installed today to stop this for good!
Fly Curtains are a really great addition to any house due to their practicality and many benefits. Fly curtains can make a home look even nicer as well as stop flies from getting in. They can come in many different colours to match your house or workplace and make it very difficult for the flies to get in.
These curtains are also very easy to install and can be done by yourself in a self-assembly setup. Please don't hesitate to speak with us to purchase these curtains in a range of colours to make your home look great!
Our local professionals nearby you aim to offer you the very best services from kitchen cleaning in Bere Ferrers to supply of fly screens closest to your spending budget and are able to work in surrounding areas too.
Kitchen Deep Cleaning in Bere Ferrers - https://www.air-duct-cleaning.co.uk/cleaning/kitchen/devon/bere-ferrers
Extraction Cleaning in Bere Ferrers - https://www.air-duct-cleaning.co.uk/cleaning/extraction/devon/bere-ferrers
School Deep Cleaning in Bere Ferrers - https://www.air-duct-cleaning.co.uk/cleaning/school/devon/bere-ferrers
PVC Strip Curtains in Bere Ferrers - https://www.air-duct-cleaning.co.uk/pvc-curtains/devon/bere-ferrers
Catering Equipment in Bere Ferrers - https://www.air-duct-cleaning.co.uk/catering-equipment/devon/bere-ferrers
If you are looking for any more information on fly screens in Bere Ferrers PL20 7 please get in touch with our experts by filling in the provided contact form.
This will allow us to provide you with a range of answers to any questions you have and also will enable you to find out even more info on our services.
We cover Bere Ferrers (Devon)


text:
Educators themselves cannot apply for this award. Instead, exemplary educators are identified by the Maryland State Department of Education which maintains a Maryland Educator Talent Bank (METB) of exemplary educators. The individuals recommended for the Talent Bank are considered for State committees, advisory panels, and special awards such as the Milken National Educator Award. Educators recommended for the METB should be early to mid-career professionals, with five to fifteen years experience in teaching or less than twenty years as administrators. Their contributions to education should be significant and they should demonstrate leadership, innovative approaches to teaching, and dedication to the field of education. Hailed as "the Oscars of Teaching" by Teacher Magazine, the Milken National Educator Awards were conceived by Lowell and Michael Milken to recognize the importance of outstanding educators and encourage talented young people to enter teaching. Unlike most teaching awards, the Milken Educator Awards have no formal nomination or application process. Each year exceptional teachers and principals can be recommended without their knowledge. The Milken Foundation makes a final decision on its Award recipients.
The Maryland State Department of Education appreciates information about outstanding candidates for the Talent Bank. If you know of an outstanding teacher, please let us know by supplying the following information on the Talented Teacher Referral Form and sending it by mail or email to the address given in the contact information below.


text:
Thunderbird is a great email client from the same people who brought you the Firefox browser. Thunderbird gives you IMAP/POP support, a built-in RSS reader, support for HTML mail, powerful quick search, saved search folders, advanced message filtering, message grouping, labels, return receipts, smart address book LDAP address completion, import tools, and the ability to manage multiple e-mail and newsgroup accounts.
Features- Tabbed email
- An Archive feature similar to the one in GMail
- Lightning fast search
- Smart folders
Download Thunderbird 5.0 Now


text:
Newt Gingrich says, when it comes to his campaigning, he has been conducting an experiment. The former House speaker says he's been running a positive campaign as he competes for the Republican nomination. And if voters who say they hate negative campaigning practice what they preach, Gingrich says he'll do better than expected in Iowa.
But Gingrich also says he needs to set the record straight, and that means firing back at Mitt Romney.
NPR's David Schaper is traveling with the Gingrich campaign.
DAVID SCHAPER, BYLINE: A barrage of harsh television commercials attacking Newt Gingrich have taken their toll. A month ago, polls had Gingrich on top of the field of presidential candidates among Iowa's Republican voters. Then the attack ads started.
SCHAPER: This one, like many of the anti-Gingrich ads, is funded by Restore Our Future, a Super PAC supporting Mitt Romney, which has spent more than $3 million attacking Gingrich.
: For a state this size, to spend that number of dollars in negative ads aimed at one candidate, is pretty amazing.
SCHAPER: But Gingrich admits they're working. Since the negative ads have been airing, Gingrich's poll numbers have plummeted. This weekend's Des Moines Register poll shows Gingrich getting the support of just 12 percent of Iowa Republicans. Gingrich was asked if he feels swift-boated. That's a reference to the 2004 ad campaign by the group Swift Boat Veterans for Truth targeting Democratic presidential candidate John Kerry. Gingrich said...
: No. I feel Romney-boated.
SCHAPER: And Gingrich has finally had enough.
: I think if you have somebody spend three and a half million dollars lying about you, you have some obligation to come back and set the record straight.
SCHAPER: First, Gingrich points out that the negative attacks on him haven't helped Romney. He says they've probably helped out former Pennsylvania Senator Rick Santorum the most, whose numbers are raising heading into Tuesday night's caucuses, while Romney's have remained steady.
: Governor Romney remains, basically, a Massachusetts moderate. And he has not broken out, despite spending millions of dollars.
SCHAPER: And, Gingrich says, he'll begin airing commercials to draw a contrast between himself and Romney. But with the caucuses taking place tomorrow night, his campaign did not say when those ads might air.
Candidates Rick Perry and Michele Bachmann say they'll skip campaigning for the next contest in New Hampshire where Romney is heavily favored. Instead, they'll head straight to South Carolina, the third presidential voting state. But not Gingrich.
: No. I think New Hampshire is the first - perfect state to have a debate over Romneycare, and to have a debate about tax paid abortions, which he signed, and to have a debate about putting Planned Parenthood on a government board, which he signed, and to have a debate about appointing liberal judges, which he did. And so I think New Hampshire is a good place to start the debate for South Carolina.
SCHAPER: At LJ's Neighborhood Bar and Grill in Waterloo last night, Gingrich told the overflowing crowd he's probably been too passive in countering the ads that he calls false. But Bill Herkelman of Cedar Falls, who works for the Blackhawk County Sheriff's Office, says the negative ads haven't changed how he feels about Gingrich.
BILL HERKELMAN: I am going to caucus for Newt Gingrich. I believe in his thoughts, I believe in his ability to lead. He is probably one of the most intelligent persons on the campaign trail, in my opinion.
SCHAPER: And Kathleen Frank, of nearby Waverly, came away impressed with Gingrich too. But she says she and her husband are not sure yet if they'll caucus for him.
KATHLEEN FRANK: We've met all of the candidates now so the next couple of days, we'll just be sorting them out and, kind of, making our decision probably at the last minute.
SCHAPER: Gingrich is actually counting on undecided voters like the Franks. Many Iowans say they still haven't made up their minds, or could change them at the caucuses. And if they end up supporting Gingrich, his decision to start hitting back might pay off.
David Schaper, NPR News in Waterloo, Iowa.
WERTHEIMER: You're listening to MORNING EDITION from NPR News. Transcript provided by NPR, Copyright NPR.


text:
Inserts / Messages
Inserts / Messages
I cannot see this too often!
It's amazing!!!
1910 Ford
Make sure you read all the statistics under the photo.
This has only been 102 years ago…Amazing!!!
Show this to your friends, children and/or grandchildren!
The year is 1910, over one hundred years ago. What a difference a century makes!
Here are some statistics for the Year 1910:
The average life expectancy for men was 47 years.
Fuel for this car was sold in drug stores only.
Only 14 percent of the homes had a bathtub.
Only 8 percent of the homes had a telephone.
There were only 8,000 cars and only 144 miles of paved roads.
The maximum speed limit in most cities was 10 mph.
The tallest structure in the world was the Eiffel Tower !
The average US wage in 1910 was 22 cents per hour.
The average US worker made between $200 and $400 per year.
A competent accountant could expect to earn $2000 per year,
a dentist $2,500 per year, a veterinarian between $1,500 and $4,000 per year,
and a mechanical engineer about $5,000 per year.
More than 95 percent of all births took place at HOME.
Ninety percent of all Doctors had NO COLLEGE EDUCATION!
Instead, they attended so-called medical schools,
many of which were condemned in the press AND the government as 'substandard.'
Sugar cost four cents a pound.
Eggs were fourteen cents a dozen.
Coffee was fifteen cents a pound.
Most women only washed their hair once a month, and used Borax or egg yolks for shampoo.
There was no such thing as under arm deodorant or tooth paste.
Canada passed a law that prohibited poor people from entering into their country for any reason.
The five leading causes of death were:
1. Pneumonia and influenza
2, Tuberculosis
3. Diarrhea
4. Heart disease
5. Stroke
The American flag had 45 stars.
The population of Las Vegas Nevada was only 30!
Crossword puzzles, canned beer, and iced tea hadn't been invented yet
There was no Mother's Day or Father's Day.
Two out of every 10 adults couldn't read or write and only 6 percent of all Americans had graduated from high school.
Eighteen percent of households had at least one full-time servant or domestic help.
There were about 230 reported murders in the ENTIRE U.S.A. !
I am now going to forward this to someone else without typing it myself.
From there, it will be sent to others all over the WORLD…all in a matter of seconds!
Try to imagine what it may be like in another 100 years.


text:
Shopping Cart:
item(s) - $0.00
My Account | Order Status | Returns | Contact Us |
New products Bestsellers On Sale Shop by Brand |
Canon 67mm Circular Polarizing Filter
Canon Circular Polarizer - Light rays which are reflected become polarized. Polarizing filters are used to select which light rays enter your camera lens. They can remove unwanted reflections from non-metallic surfaces such as water or glass and also saturate colors providing better contrast. The effect can be seen through the viewfinder and changed by rotating the filter. The filter factor varies according to how the filter is rotated and its orientation to the sun.
If you're out walking on a lovely day - in the mountains or at the beach - and you want to get a fabulous shot of a cloud-filled sky or make the water seem more saturated, then a polarizer is the way to go. This filter is the best way to make the clouds stand out, increase or decrease the saturation of the ocean or increase or decrease the reflection off the water. You can also use this filter when shooting into glass or windows since it will, again, either increase or decrease reflections.
If you're shooting black and white and want to simulate a threatening storm, try throwing on a #25 Red filter. The vista will take on the appearance of an imminent, ominous storm.
Along with a UV or Skylight Filter, a polarizing filter should be a part of everyone's gear bag. It can turn a run-of-the-mill image into a stunning, creative photo by increasing color saturation.
Note! Circular polarizers are specifically designed for use with auto-focus SLR cameras (They will also work on manual systems and video cameras without problems)
This filter eliminates ultraviolet rays to remove haze from outdoor shots as well as polarizing the light to remove reflections, and increase color saturation, without affecting the overall color balance
Type- Circular Polarizer Size - 67mm
Grade- Not Applicable
Filter Factor- Between 2.3 and 2.8 (approx. +1.3 stops)
Multi-Coated- Not Applicable
Rotating - Yes
Effect- Removes reflections and increases color saturation without affecting the overall color balance
Application- Nature, travel, outdoor photography
Color Temperature- Not Applicable
Construction- ColorCore Glass
Front Filter Thread Size- 67mm
Front Lens Cap Size- 67mm |