#16998 closed defect (invalid)
sqlite3 3.6.4 configure error - failure to find $NAWK
Reported by: | tla@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.6.0 |
Keywords: | sqlite configure awk | Cc: | |
Port: | sqlite3 |
Description
I have had sqlite3 fail to build on two different systems now (both Intel Macs running Leopard) with the following error:
Error: Target org.macports.build returned: shell command " cd "/opt/local/var/macports/build/very/long/dirname/work/sqlite-3.6.4" && gnumake all " returned error 2 Command output: sed -e s/--VERS--/3.6.4/ ./src/sqlite.h.in | \ sed -e s/--VERSION-NUMBER--/3006004/ >sqlite3.h /usr/bin/gcc-4.0 -O2 -o mkkeywordhash -DSQLITE_OMIT_LOAD_EXTENSION=1 ./tool/mkkeywordhash.c ./mkkeywordhash >keywordhash.h /usr/bin/gcc-4.0 -O2 -o lemon ./tool/lemon.c cp ./tool/lempar.c . cp ./src/parse.y . ./lemon -DSQLITE_OMIT_LOAD_EXTENSION=1 parse.y mv parse.h parse.h.temp f ./addopcodes.awk parse.h.temp >parse.h /bin/sh: f: command not found gnumake: [parse.c] Error 127 (ignored) cat parse.h ./src/vdbe.c | -f ./mkopcodeh.awk >opcodes.h /bin/sh: -f: command not found cat: stdout: Broken pipe gnumake: *** [opcodes.h] Error 127
Look at it, the culprit seemed in both cases to be an empty NAWK in the Makefile. When I go to the build directory and re-run ./configure, NAWK is populated correctly. I can then run 'make clean && make' in the normal way.
After this is done, in both cases I returned to my original 'port install' command to continue installation of whatever depended on sqlite3. I got the following warning, which I include just in case it signifies something other than "I had to go fix the build manually":
---> Building sqlite3 with target all ---> Staging sqlite3 into destroot Warning: violation by /System Warning: violation by /usr Warning: sqlite3 violates the layout of the ports-filesystems! Warning: Please fix or indicate this misbehavior (if it is intended), it will be an error in future releases! ---> Installing sqlite3 3.6.4_0 ---> Activating sqlite3 3.6.4_0 ---> Cleaning sqlite3
Change History (3)
comment:1 Changed 16 years ago by raimue (Rainer Müller)
Resolution: | → invalid |
---|---|
Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
Don't run
./configure
manually! You are missing important arguments, which control where stuff gets installed. Now it did install stuff outside of your prefix (/opt/local by default). Reinstall sqlite3 to fix this or other ports using sqlite3 will fail or build incorrectly.The real problem and answer is given here: LeopardProblems