Forums : Technical Issue Help
Dear Open Hub Users,
We’re excited to announce that we will be moving the Open Hub Forum to
https://community.blackduck.com/s/black-duck-open-hub.
Beginning immediately, users can head over,
register,
get technical help and discuss issue pertinent to the Open Hub. Registered users can also subscribe to Open Hub announcements here.
On May 1, 2020, we will be freezing https://www.openhub.net/forums and users will not be able to create new discussions. If you have any questions and concerns, please email us at
info@openhub.net
autoconf code detection wrong
If you look at the code analysis for both FFmpeg and MPlayer you will see some code that is claimed to be autoconf:
https://www.ohloh.net/p/mplayer/analyses/latest
https://www.ohloh.net/p/ffmpeg/analyses/latest
I can assure you that neither project contains not even a single line of autoconf code, nor will they in the future :)
best regards, Diego
Yes, this is a bug in our source code detector.
If we find a file called configure
, and it parses as a shell script, we consider it to be Autoconf.
A true Autoconf file would probably contain somewhere within it the phrase generated by GNU Autoconf
or something similar. I can open a ticket for this bug.
Thanks,
Robin
https://sourceforge.net/apps/trac/ohcount/ticket/62
AFAIK autoconf configure scripts are always accompanied by the configure.ac/configure.in files from which they were generated.
This is another reasonably robust heuristics that you can use to identify configure scripts generated by autoconf.