[ADMB Users] Please test updated installation documentation.

Jon Schnute schnutej-dfo at shaw.ca
Sat Nov 16 17:42:41 PST 2013

Further to my previous message, I have now tried the same experiment using
the version 11.1 source code, rather than ADMB-latest. I discovered that
this version produces a much smaller Unix tree in the directory
..\admb\utilities\mingw, so I used the ..\mingw tree that I downloaded from
the latest. (I just replaced the 11.1 ..\mingw directory with the new one
obtained today.) Then I tried to make the 11.1 binary ADMB library as
before, and again the process failed while trying to compile 'amoeba.cpp'. 


Does amoeba.cpp require something special? Are both of you getting this same
problem? I'm taking care to ensure that nothing on my path would override
the Unix tools at ..\admb\utilities\mingw.


Incidentally, for step 5 I used '\utilities\make' rather than 'make' as
stated in my previous message. On this point, why do you use a possibly old
version of 'make' embedded in the ADMB source code, rather than the version
of 'make' that currently comes with mingw/msys?


These problems help illustrate the reasons that I flagged this as an
important issue. I'm not blaming anyone, but I hope you'll stay with this
until the problems are resolved.




PS - I really sympathize with Dave's question: "Doesn't anyone test this
stuff?" I think the ADMB project needs some volunteer testers who at least
check each new release on each OS. I'm trying to play that role in this
exercise, at least for the Windows OS.


PPS - I wonder why the version of mingw that Dave obtained yesterday worked,
whereas the version obtained with get-mingw.bat appears not to. 


From: Jon Schnute [mailto:schnutej-dfo at shaw.ca] 
Sent: November-16-13 4:28 PM
To: 'Johnoel Ancheta'; 'dave fournier'
Cc: 'ADMB Users'
Subject: RE: [ADMB Users] Please test updated installation documentation.


Johnoel and Dave - Thanks for the updated documentation. I've tried to
follow it carefully, starting with the file admb-latest.zip obtained via
your link:




>From this I manually extracted the 'admb' directory tree to D:\Temp\admb.
That's essentially step 2,  where I've used a slightly different directory
than you suggested. I then used a command window to install mingw:


D:\Temp\admb\> utilities\get-mingw.bat


That seemed to work fine, giving me a fully populated tree at
D:\Temp\admb\utilities\mingw. Furthermore, I get g++ version 4.8.1 with the


D:\Temp\admb\utilities\mingw\bin>g++ --version

g++ (GCC) 4.8.1


I presume this is a 32-bit compiler, right? Anyway I'm now done with step 4.


To implement step 5, I used the command:




This seemed to be working nicely for a while  until it failed suddenly while
trying to compile the file amoeba.cppp. Here is the final console of


***** Final screen

g++ -c -O3 -Wall -DSAFE_ALL -D__GNUDOS__ -Dlinux -D__SPDLL__ -DUSE_LAPLACE

build\dist\include -o..\build\objects\dist\saflp-linad99-vrannegbin.obj


g++ -c -O3 -Wall -DSAFE_ALL -D__GNUDOS__ -Dlinux -D__SPDLL__ -DUSE_LAPLACE

build\dist\include -o..\build\objects\dist\saflp-linad99-vregress.obj


g++ -c -O3 -Wall -DSAFE_ALL -D__GNUDOS__ -Dlinux -D__SPDLL__ -DUSE_LAPLACE

build\dist\include -o..\build\objects\dist\saflp-linad99-vspline.obj


g++ -c -O3 -Wall -DSAFE_ALL -D__GNUDOS__ -Dlinux -D__SPDLL__ -DUSE_LAPLACE

build\dist\include -o..\build\objects\dist\saflp-linad99-vtdev.obj


g++ -c -O3 -Wall -DSAFE_ALL -D__GNUDOS__ -Dlinux -D__SPDLL__ -DUSE_LAPLACE

build\dist\include -o..\build\objects\dist\saflp-linad99-xfmmtr1.obj


g++ -c -O3 -Wall -DSAFE_ALL -D__GNUDOS__ -Dlinux -D__SPDLL__ -DUSE_LAPLACE

build\dist\include -o..\build\objects\dist\saflp-linad99-xgradclc.obj


g++ -c -O3 -Wall -DOPT_LIB -D__GNUDOS__ -Dlinux -D__SPDLL__ -DUSE_LAPLACE

uild\dist\include -o..\build\objects\dist\optlp-nh99-adsleep.obj


g++ -c -O3 -Wall -DOPT_LIB -D__GNUDOS__ -Dlinux -D__SPDLL__ -DUSE_LAPLACE

uild\dist\include -o..\build\objects\dist\optlp-nh99-amoeba.obj

process_begin: CreateProcess(NULL, cat ../VERSION, ...) failed.

***** End of final screen


This is a bit weird, perhaps the result of recent changes to the source
code. But rest assured that I'm taking everything written by both of you
very seriously. I really appreciate your efforts.




From: users-bounces at admb-project.org [mailto:users-bounces at admb-project.org]
On Behalf Of Johnoel Ancheta
Sent: November-16-13 12:04 PM
To: dave fournier
Cc: ADMB Users
Subject: Re: [ADMB Users] Please test updated installation documentation.


Ahh, thanks for the feedback.  I assume that you are using




Which failed at step 5


On Sat, Nov 16, 2013 at 9:55 AM, dave fournier <davef at otter-rsch.com> wrote:

So then I installed the msys tools using the installer at.  Note that I ONLY
installed the tools since the comiler is presumably already installed with




on my path.

Check by  using commands like rm and cp.  OK so far.

Users mailing list
Users at admb-project.org


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.admb-project.org/pipermail/users/attachments/20131116/8abd725a/attachment.html>

More information about the Users mailing list