Add FreeBSD to TravisCI config

[jbeich]

TravisCI supports FreeBSD nowadays. Let's see how well it works.

This is an alterantive to #66 in case you don't want to sign up the repo with CirrusCI or maintain two CI configs.

[philshafer]

I use the “script” line to give me information about the build so I can more easily reproduce issues. Can you change be done in a way that retains this? Thanks, Phil

…

On Nov 24, 2020, at 1:01 PM, Jan Beich ***@***.***> wrote: @jbeich commented on this pull request. In .travis.yml <#72 (comment)>: > @@ -1,6 +1,19 @@ language: c -script: printenv && uname -a && ls -l && /bin/sh -x ./bin/setup.sh && cd build && ../configure --enable-warnings && make && sudo make install && make test +os: +- linux +- freebsd + +before_install: + - export CC=cc CXX=c++ Not necessary after travis-ci/travis-build#1915 <travis-ci/travis-build#1915> — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#72 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAROIOEB5SWZTIFGNKBZNMDSRPYIXANCNFSM4NHEK7PQ>.

[jbeich]

Like this? I can't test on TravisCI anymore due to usage limits but see https://travis-ci.org/github/Juniper/libxo/builds/746617293

[philshafer]

“../configure" fails, but we can’t see the “config.log” output file. Can we get a copy of that? Thanks, Phil

…

On Nov 29, 2020, at 2:53 PM, Jan Beich ***@***.***> wrote: Like this? I can't test on TravisCI anymore due to usage limits but see https://travis-ci.org/github/Juniper/libxo/builds/746616668 <https://travis-ci.org/github/Juniper/libxo/builds/746616668> — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#72 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAROIOE7PZIGO3JCEOVXHBDSSKRELANCNFSM4NHEK7PQ>.

[jbeich]

If you'd like to switch to GitHub Actions in future, see actions/runner#385 (comment)

[jbeich]

“../configure" fails, but we can’t see the “config.log” output file.

It doesn't fail anymore. I've updated the above comment to point to a more recent build. No clue why CI status doesn't propagate to this PR: maybe you need to re-install TravisCI from marketplace.

See also https://travis-ci.community/t/github-status-not-posted-on-commits-on-repositories-using-legacy-service-integration/7798