In my previous post, I described how to build an old version of GNU Make for Windows. While working on that I wanted to be able to test out different versions of Visual Studio to see if it builds successfully. Quickly switching between versions of Visual Studio was difficult so I created a batch file to help make it a lot easier.
This script takes a single argument that specifies which version of visual studio you want to set up and it then calls the appropriate vsvars32.bat file for that version of Visual Studio.
@echo off
if "%1" == "vs4" goto vs4
if "%1" == "vs6" goto vs6
if "%1" == "vs2003" goto vs2003
goto argerror
:vs4
pushd C:\msdev\bin
call vcvars32 x86
popd
goto done
:vs6
pushd C:\Program Files\Microsoft Visual Studio\VC98\Bin
call vcvars32
popd
goto done
:vs2003
pushd "C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\Tools\"
call vsvars32.bat
popd
goto done
:argerror
echo no Visual Studio version specified!
echo usage: setupenv [version]
echo where version is one of the following: vs4, vs6, vs2003
:done
I needed to build GNU Make v3.8 for Windows, turns out that this is not straightforward and I needed to patch the build script to get it to correctly build. GNU Make 3.8 is a very old version of make, the release note dates back to 2002.
The first issue is it needs an old version of Visual C++, trying to build using VS 2019 you will get a lot of warnings about deprecated flags. Reading the README.W32 file it mentions MSVC 5.x and MSVC 6.x. I opted for MSVC 6 which I happened to have a copy of in a Windows 2000 VM.
The first issue we need to resolve is a linking error caused by a missing library.
Looking through the build output we can see that it cannot find "config.h", which prevents the "subproc.lib" library from compiling which subsequently causes the error we just saw.
C:\BUILD\xxx\make-3.80\w32\subproc>cl.exe /nologo /MT /W3 /GX /Z7 /YX /Od /I .. /I . /I ../include /I ../.. /D WIN32 /D
WINDOWS32 /D _DEBUG /D _WINDOWS /FR.\WinDebug/ /Fp.\WinDebug/subproc.pch /Fo.\WinDebug/ /c sub_proc.c
sub_proc.c
sub_proc.c(9) : fatal error C1083: Cannot open include file: 'config.h': No such file or directory
The reason that "config.h" does not exist is that the file is not created by the build script. The line in the build script that creates it doesn’t get run, this is because there is a “+” at the beginning of the line which stops this line from running.
set make=gnumake
+if not exist config.h copy config.h.W32 config.h
cd w32\subproc
Removing the plus at the beginning of the line allows "subproc.lib" to be compiled and linked, but we still get linker errors.
C:\BUILD\xxx\make-3.80>echo WinRel\pathstuff.obj 1>>link.rel
C:\BUILD\xxx\make-3.80>echo off
"Linking WinRel/gnumake.exe"
function.obj : error LNK2001: unresolved external symbol _hash_init
variable.obj : error LNK2001: unresolved external symbol _hash_init
file.obj : error LNK2001: unresolved external symbol _hash_init
dir.obj : error LNK2001: unresolved external symbol _hash_init
read.obj : error LNK2001: unresolved external symbol _hash_init
variable.obj : error LNK2001: unresolved external symbol _hash_insert_at
file.obj : error LNK2001: unresolved external symbol _hash_insert_at
dir.obj : error LNK2001: unresolved external symbol _hash_insert_at
read.obj : error LNK2001: unresolved external symbol _hash_insert_at
variable.obj : error LNK2001: unresolved external symbol _hash_deleted_item
file.obj : error LNK2001: unresolved external symbol _hash_deleted_item
dir.obj : error LNK2001: unresolved external symbol _hash_deleted_item
read.obj : error LNK2001: unresolved external symbol _hash_deleted_item
variable.obj : error LNK2001: unresolved external symbol _hash_find_slot
file.obj : error LNK2001: unresolved external symbol _hash_find_slot
dir.obj : error LNK2001: unresolved external symbol _hash_find_slot
read.obj : error LNK2001: unresolved external symbol _hash_find_slot
variable.obj : error LNK2001: unresolved external symbol _hash_find_item
file.obj : error LNK2001: unresolved external symbol _hash_find_item
dir.obj : error LNK2001: unresolved external symbol _hash_find_item
function.obj : error LNK2001: unresolved external symbol _hash_find_item
variable.obj : error LNK2001: unresolved external symbol _hash_free
read.obj : error LNK2001: unresolved external symbol _hash_free
function.obj : error LNK2001: unresolved external symbol _hash_free
variable.obj : error LNK2001: unresolved external symbol _hash_map
file.obj : error LNK2001: unresolved external symbol _hash_map
variable.obj : error LNK2001: unresolved external symbol _hash_delete
file.obj : error LNK2001: unresolved external symbol _hash_delete
variable.obj : error LNK2001: unresolved external symbol _hash_print_stats
file.obj : error LNK2001: unresolved external symbol _hash_print_stats
variable.obj : error LNK2001: unresolved external symbol _hash_map_arg
file.obj : error LNK2001: unresolved external symbol _hash_dump
dir.obj : error LNK2001: unresolved external symbol _hash_insert
function.obj : error LNK2001: unresolved external symbol _hash_insert
function.obj : error LNK2001: unresolved external symbol _hash_load
.\WinRel/gnumake.exe : fatal error LNK1120: 13 unresolved externals
"WinRel build failed"
C:\BUILD\xxx\make-3.80>
There’s a lot of unresolved symbols, I searched for "hash_insert_at" and found the definition for it in "hash.c". Looking through the build script it turns out that this file is not included in the build. I added the following two lines to "build_w32.bat" just after "implicit.c" is compiled.
C:\BUILD\build\make-3.80>echo off
"Linking WinRel/gnumake.exe"
LINK : warning LNK4089: all references to "ADVAPI32.dll" discarded by /OPT:REF
"WinRel build succeeded!"
C:\BUILD\build\make-3.80>
We use cookies on our website to give you the most relevant experience by remembering your preferences and repeat visits. By clicking “Accept All”, you consent to the use of ALL the cookies. However, you may visit "Cookie Settings" to provide a controlled consent.
This website uses cookies to improve your experience while you navigate through the website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may affect your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
Cookie
Duration
Description
cookielawinfo-checkbox-analytics
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
cookielawinfo-checkbox-functional
11 months
The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
cookielawinfo-checkbox-necessary
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
cookielawinfo-checkbox-others
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.
cookielawinfo-checkbox-performance
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".
viewed_cookie_policy
11 months
The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.