Problems building on FreeBSD

[pgiffuni]

I noticed two outstanding issues when I last triedto port this to FreeBSD:

1. The shebang on file configure is wrong:

% file /bin/bash
/bin/bash: cannot open `/bin/bash' (No such file or directory)

You could use "!/usr/bin/env bash" or you could port it to bin/sh and run the checkbashism script, that Debian carries, on it.

% make configure
===>   scancode-toolkit-2.2.1 depends on executable: bash - found
===>   scancode-toolkit-2.2.1 depends on file: /usr/local/bin/python2.7 - found
===>  Configuring for scancode-toolkit-2.2.1
===>   FreeBSD 10 autotools fix applied to /usr/ports/devel/scancode-toolkit/work/scancode-toolkit-2.2.1/tests/textcode/data/hard_to_parse/configure
Traceback (most recent call last):
  File "/usr/ports/devel/scancode-toolkit/work/scancode-toolkit-2.2.1/etc/configure.py", line 79, in <module>
    raise Exception('Unsupported OS/platform %r' % sys_platform)
Exception: Unsupported OS/platform 'freebsd11'

...
Kai Knoblich has been working on a port much more diligently and his WIP is here:

https://reviews.freebsd.org/D16484

[pombredanne]

@pgiffuni This is awesome work from Kai Knoblich, you, @miwi-fbsd and @mat813 .... let me reply shortly and help you the best I can for this port!

I guess I can likely get a user name and make comments directly at https://reviews.freebsd.org/D16484 ?

Note that using the latest 2.9.2 pre release of 3.0 is definitely the way to go (and not 2.2.1 which is oh-so-old)

[knobix]

Thank you for your feedback. The review for scancode-toolkit on FreeBSD's phabricator has been updated to match the latest version (= 2.9.7) in your repository.

The outsourcing of the platform-specific binaries into separate Python packages is a nice solution to make scancode-toolkit more platform independent.

Regarding your question to get an account on FreeBSD's phabricator: Yes, that is possible. Simply create here an new account: https://reviews.freebsd.org/auth/register/

[knobix]

Since January 2019 scancode-toolkit is available as a port on FreeBSD.

This issue can actually be closed from my point of view but I would like to open a PR for src/commoncode/system.py that needs to be patched to make scancode-toolkit run on FreeBSD.

Would it be ok to open a new PR and use this issue as a reference for it?

[pombredanne]

This was autoclosed by GitHub...
I think we should may be also add it to https://github.com/nexB/scancode-toolkit/blob/develop/etc/configure.py and I can help with crafting plugins for native code pointing to actual FreebSD installed packages binaries too

[pombredanne]

We should be adding a FreeBSD CI test run with Cirrus IMHO

See https://github.com/YutaroHayakawa/generic-ebpf/blob/3685ece59da8258d3553f50f31cada02ce75299e/.cirrus.yml#L4 ...

Help welcome

[knobix]

Thank you for merging #1695 and sorry for late reply! Indeed, it makes sense to align configure.py and also add a CI test for FreeBSD. Both are great ideas and I'll come back to them as soon as possible.

At the moment I'm still testing the Python 2.7 and Python 3.6 variants of the scancode 3.1.x release against the available Python ports in the FreeBSD ports tree.

[knobix]

So, as promised in my previous comment I created PR #1724 that implements the following items:

• Add Cirrus CI support for FreeBSD (the .cirrus.yml file will evolve during the further progress)
• Add pip build/install support for https://github.com/nexB/scancode-toolkit/blob/develop/etc/configure.py and https://github.com/nexB/scancode-toolkit/blob/develop/etc/conf/base.py
• Change the shebang usage of https://github.com/nexB/scancode-toolkit/blob/develop/configure (which was reported by @pgiffuni in this issue report).

At the moment the build via pip still fails on FreeBSD because some packages aren't available for FreeBSD:

• pyahocorasick (FreeBSD ports/pkg version is available
• url (only for releases >= 0.4.x, FreeBSD ports/pkg is available
• extractcode-p7
• extractcode-libarchive
• typecode-libmagic