[Bug 215184] security/hashcat-legacy: hard-coded gcc can cause build failure
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Fri Dec 9 22:33:40 UTC 2016
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215184
Bug ID: 215184
Summary: security/hashcat-legacy: hard-coded gcc can cause
build failure
Product: Ports & Packages
Version: Latest
Hardware: Any
OS: Any
Status: New
Severity: Affects Some People
Priority: ---
Component: Individual Port(s)
Assignee: freebsd-ports-bugs at FreeBSD.org
Reporter: z7dr6ut7gs at snkmail.com
CC: lifanov at mail.lifanov.com
Flags: maintainer-feedback?(lifanov at mail.lifanov.com)
CC: lifanov at mail.lifanov.com
If you have lang/gccXY installed, but not lang/gcc, currently there is no
/usr/local/bin/gcc. If you are on FreeBSD 10 or later, there is also no
/usr/bin/gcc by default. But the hashcat-legacy-2.00/src/Makefile hard-codes
the compiler to gcc (or some other spellings if you're cross-compiling to
windows for instance) instead of referring to ${CC} that the ports
infrastructure defines.
The result:
===> hashcat-legacy-2.00_1 depends on executable: gmake - found
===> Returning to build of hashcat-legacy-2.00_1
===> hashcat-legacy-2.00_1 depends on executable: gcc46 - found
===> hashcat-legacy-2.00_1 depends on file: /usr/local/bin/as - found
===> hashcat-legacy-2.00_1 depends on shared library: libgmp.so - found
(/usr/local/lib/libgmp.so)
===> Configuring for hashcat-legacy-2.00_1
===> Building for hashcat-legacy-2.00_1
gmake[1]: Entering directory
'/wrkdirs/usr/ports/security/hashcat-legacy/work/hashcat-legacy-2.00'
gcc -W -Wall -pipe -I include/ -O2 -s -fomit-frame-pointer -funroll-loops
-I/opt/hashcat-deps/gmp/linux64/include -D__HC_x86_64__ -DPOSIX -m64 -msse2 -c
src/common.c -o obj/common.LINUX.64.o
gmake[1]: gcc: Command not found
gmake[1]: *** [src/Makefile:190: obj/common.LINUX.64.o] Error 127
gmake[1]: Leaving directory
'/wrkdirs/usr/ports/security/hashcat-legacy/work/hashcat-legacy-2.00'
*** Error code 1
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ports-bugs
mailing list