 
            Hi Brad,
2017-07-15 0:41 GMT+08:00 Bradley Lucier lucier@math.purdue.edu:
On 07/14/2017 04:56 AM, Adam wrote:
2017-06-15 2:28 GMT+08:00 Bradley Lucier <lucier@math.purdue.edu mailto: lucier@math.purdue.edu>:
On 06/11/2017 05:08 AM, Adam wrote: so the following is how to properly switch it on right?: git clone https://github.com/gambit/gambit.git <https://secure-web.cisco.com/1homFLxKQnlcP85KH6ygKE6lEkPYiKxcHhttZ-GD8a4kbxAqz92WpuVjIm6ikIv6UPxFW5clU4WZjJdIxlmbhNR0ba XZR0vJAt4Z8JLeUlHXGKOILBkDBSjGt317Y2kqUNI7KeGx154F3IhNZrTta_ 58NQ7wxSItoMSjKHkHKlzC2sd0pYjzv8MoquuM7aX_GqZEHOEIIyTBULxwYR CYr_6tRG4ok7DUpsX528uh7N99_N0P2QJpcQjApry7sLOhOR_iW1PDDl7QTw MNdheuaXLqcqElrl_n1Lmdd70nBf4vusB_9p799fwCttJElIskMR2HhrFIk1 vCWmhwsXBHyStv75-j7cpQVkpJ9X16ElNg/https%3A%2F%2Fgithub.com% 2Fgambit%2Fgambit.git> cd gambit ./configure --enable-auto-force make -j4 mv gsc/gsc gsc-boot make bootclean make -j4 sudo make install
Or do you suggest any other sequence or way? Should I use "from-scratch" instead of "make bootclean" + "make"? This appears to build an executable: 29 18:34 git clone https://github.com/gambit/gambit.git <https://secure-web.cisco.com/1homFLxKQnlcP85KH6ygKE6lEkPYiKxcHhttZ-GD8a4kbxAqz92WpuVjIm6ikIv6UPxFW5clU4WZjJdIxlmbhNR0ba XZR0vJAt4Z8JLeUlHXGKOILBkDBSjGt317Y2kqUNI7KeGx154F3IhNZrTta_ 58NQ7wxSItoMSjKHkHKlzC2sd0pYjzv8MoquuM7aX_GqZEHOEIIyTBULxwYR CYr_6tRG4ok7DUpsX528uh7N99_N0P2QJpcQjApry7sLOhOR_iW1PDDl7QTw MNdheuaXLqcqElrl_n1Lmdd70nBf4vusB_9p799fwCttJElIskMR2HhrFIk1 vCWmhwsXBHyStv75-j7cpQVkpJ9X16ElNg/https%3A%2F%2Fgithub.com% 2Fgambit%2Fgambit.git> 30 18:34 cd gambit 31 18:34 ./configure 32 18:34 make -j4 current-gsc-boot 35 18:37 ./configure --enable-single-host --enable-auto-forcing 36 18:37 make -j 8 from-scratch
It fails Test 1 of "make check", but I don't know whether that's relevant. BradBrad,
What you suggested now would be how to build the current beta SMP Gambit, currently during its period of lots of deep changes, which is a transitory period, right? -
I don't understand this, sorry.
(Nevermind.)
Let's nail how to do it in the 'ordinary' case too, so that would be in a
while from now, and, for older Gambit versions. Would it be like this?:
./configure --enable-auto-forcing make from-scratch cp gsc/gsc ./gsc-boot make clean make sudo make install
Again, I'm a bit confused. I recommend the sequence of commands I already gave to build with --enable-auto-forcing:
git clone https://github.com/gambit/gambit.git cd gambit ./configure make -j 4 current-gsc-boot ./configure --enable-single-host --enable-auto-forcing make -j 4 from-scratch make -j 4 doc sudo make install
Ah, great.
The "current-gsc-boot" basically builds Gambit and then puts that particular Gambit (./gsc/gsc) in ./gsc-boot ( https://github.com/gambit/gambit/blob/08730be98e86d15eae9da5e5de8cf1d2f9c353...). Neat.
And the "from-scratch" makes a really deep wipe i.e. including the pregenerated .C files, and then a total build ( https://github.com/gambit/gambit/blob/08730be98e86d15eae9da5e5de8cf1d2f9c353... ).
Neat.
Thanks for clarifying.
So this is the long term best practice, and any change of that at any point would evoke discussion here on the ML.