I tested it and it works (you need to remove the git pull step as this is already done by gitlab ci).
regards, Nikos
On Wed, Jan 20, 2016 at 8:13 PM, Niels Möller nisse@lysator.liu.se wrote:
Nikos Mavrogiannopoulos n.mavrogiannopoulos@gmail.com writes:
On Mon, Dec 21, 2015 at 11:25 AM, Niels Möller nisse@lysator.liu.se wrote:
- script:
- git submodule update --init && autoreconf -fvi &&
./.bootstrap is nettle's advertised method to generate files needed pre-configure. So I think it's better to use that than autoreconf.
Why submodule, is nettle used as a submodule of gnutls, or is it some magic for the continuous integration system?
Seems like a copy paste thing from the gnutls file. I suggest that you setup the configurations that you like and send me to test.
Sorry for the late reply. I think this could be quite useful.
Do you think this file looks ok? Is there any easy way to test before checking it in?
-----8<--------- Build and Check (x86-64): script:
- git pull && ./.bootstrap && ./configure --disable-documentation && make -j4 && make check -j4
tags:
- x86-64
except:
- tags
Build and Check (x86): script:
- git pull && ./.bootstrap && ./configure --disable-documentation && make -j4 && make check -j4
tags:
- x86
except:
- tags
-----8<---------
I don't quite understand the details, e.g, environment in which the script is run. If it's in a fresh git checkout, I guess git pull can be omitted?
Regards, /Niels
-- Niels Möller. PGP-encrypted email is preferred. Keyid C0B98E26. Internet email is subject to wholesale government surveillance.