I'm on Mac OS X 10.8.2. I install Ruby+RVM using the RailsInstaller, so I am currently on ruby-1.9.3-p194. My application uses Rails 3.2.11.
When I run bundle install, here's the error I see:
Gem::Installer::ExtensionBuildError: ERROR: Failed to build gem native extension.
/usr/local/rvm/rubies/ruby-1.9.3-p194/bin/ruby extconf.rb --with-pg-config=/usr/bin/pg_config
Using config values from /usr/bin/pg_config
checking for libpq-fe.h... yes
checking for libpq/libpq-fs.h... yes
checking for pg_config_manual.h... yes
checking for PQconnectdb() in -lpq... yes
checking for PQconnectionUsedPassword()... yes
checking for PQisthreadsafe()... yes
checking for PQprepare()... yes
checking for PQexecParams()... yes
checking for PQescapeString()... yes
checking for PQescapeStringConn()... yes
checking for PQescapeLiteral()... yes
checking for PQescapeIdentifier()... yes
checking for PQgetCancel()... yes
checking for lo_create()... yes
checking for pg_encoding_to_char()... yes
checking for pg_char_to_encoding()... yes
checking for PQsetClientEncoding()... yes
checking for PQlibVersion()... yes
checking for PQping()... yes
checking for rb_encdb_alias()... yes
checking for rb_enc_alias()... no
checking for PGRES_COPY_BOTH in libpq-fe.h... no
checking for PGRES_SINGLE_TUPLE in libpq-fe.h... no
checking for struct pgNotify.extra in libpq-fe.h... yes
checking for unistd.h... yes
checking for ruby/st.h... yes
creating extconf.h
creating Makefile
make
compiling pg.c
pg.c: In function ‘Init_pg_ext’:
pg.c:384: error: ‘PQPING_OK’ undeclared (first use in this function)
pg.c:384: error: (Each undeclared identifier is reported only once
pg.c:384: error: for each function it appears in.)
pg.c:386: error: ‘PQPING_REJECT’ undeclared (first use in this function)
pg.c:388: error: ‘PQPING_NO_RESPONSE’ undeclared (first use in this function)
pg.c:390: error: ‘PQPING_NO_ATTEMPT’ undeclared (first use in this function)
make: *** [pg.o] Error 1
Please note that this is not an issue with pg_config. The responses to similar questions here on StackOverflow all indicate that this binary is missing (or is not found), hence the issue for the error. This seems to be a different problem, as far as I can see.
Any ideas on how I can go about fixing this issue?
Thanks!
Ringo
I used homebrew to install pg and that solved my problems:
$ brew install postgres
Related
I'm trying to start the next phase of my compiler project and I get this error when compiling
/usr/lib/gcc/x86_64-linux-gnu/7/../../../x86_64-linux-gnu/libfl.so: undefined reference to `yylex'
collect2: error: ld returned 1 exit status
Makefile:82: recipe for target 'gpl' failed
i went back to previous phases, did a make clean and recompiled and none of it compiles now, same error (it did before). This happened after I upgraded to Ubuntu 18.04. I checked for further upgrades afterwords to see if any of the required packages needed an update and there's none. Does anyone have any idea why this stopped working after the update? (possibly config file or something?)
You can either link the static library (libfl.a) or use the --as-needed linker flag.
I am getting this error When i have Started the apache server
Starting httpd: /usr/sbin/httpd: symbol lookup error: /usr/sbin/httpd:
undefined symbol: apr_bucket_alloc_aligned_floor
Please help me on this.
i got this error too this morning, it was a module conflict.
Removed the conflicting module, then ran easyapache 4 and reprovisioned the profile in WHM.
The conflicting module was:
Error: Multilib version problems found. This often means that the root
cause is something else and multilib version checking is just
pointing out that there is a problem. Eg.:
1. You have an upgrade for ea-apache24-mod_cloudflare which is missing some
dependency that another package requires. Yum is trying to
solve this by installing an older version of ea-apache24-mod_cloudflare of the
different architecture. If you exclude the bad architecture
yum will tell you what the root cause is (which package
requires what). You can try redoing the upgrade with
--exclude ea-apache24-mod_cloudflare.otherarch ... this should give you an error
message showing the root cause of the problem.
2. You have multiple architectures of ea-apache24-mod_cloudflare installed, but
yum can only see an upgrade for one of those arcitectures.
If you don't want/need both architectures anymore then you
can remove the one with the missing update and everything
will work.
3. You have duplicate versions of ea-apache24-mod_cloudflare installed already.
You can use "yum check" to get yum show these errors.
...you can also use --setopt=protected_multilib=false to remove
this checking, however this is almost never the correct thing to
do as something else is very likely to go wrong (often causing
much more problems).
Protected multilib versions: ea-apache24-mod_cloudflare-1.2.0-.5.47.x86_64 != ea-apache24-mod_cloudflare-1.2.0-.5.37.i686
Run yum update to see the error, or what ever command your OS has to check for updates.
Regards,
Tommy
If dealing with cPanel, check for updates via yum. In my case, updates were needed, so updated all yum packages.
I then found PHP scripts were not being parsed. Check that the PHP handler is set to whatever your handler should be. In my case, the handler was set to "None".
I hope this helps!
I am trying to develop applications with Eclipse / Linux for Stellaris Launchpad (LM4F120). I am following this guide: http://kernelhacks.blogspot.de/2012/11/the-complete-tutorial-for-stellaris.html
However, I can't compile StellarisWare with make:
adc.c:1: error: bad value (cortex-m4) for -mcpu= switch
adc.c:1: error: invalid floating point option: -mfpu=fpv4-sp-d16
Obviously for compilation 'cc' instead of arm-*-gcc is used. How can I circumvent this problem?
I am using gcc-arm-none-eabi-4_7-2012q4. I did the following things for both a) the full StellarisWare Package (SW-LM3S-9453.exe) and the one for the Stellaris Launchpad (SW-EK-LM4F120XL-9453.exe):
1. Unzip: ../SW-*.zip
2. Try to compile: make
please follow the instruction in the below article
http://www.embeddedcircle.com/stellaris-lm4f120-launchpad-compiling-in-ubuntu-12-04/
do not forget to set the compiler path as per instruction 4
Anyone have a clue what this error means and how to fix it?
2011-02-03 16:11:54.729 Validation[8584:607] * Warning: Defaulting to the standard codesign tool
warning: The dwarfdump binary must exist and must be executable: /usr/bin/dwarfdump (-19036)
Unable to validate your application. - (null)
According to this page, you might be able to fix this by adding a symlink to dwarfdump. However, that didn't work for me and I ended up reinstalling Xcode, which did work.
What does "The dwarfdump binary must exist and must be executable" mean?
I'm trying to debug an objective C program. It used to run, and I'm not sure what changes could have broken it, but it no longer runs at all. In the debugger, I now get:
.
.
.
unable to read unknown load command 0x80000022
unable to read unknown load command 0x80000022
unable to read unknown load command 0x80000022
Program loaded.
sharedlibrary apply-load-rules all
run
Error calling thread_get_state for GP registers for thread 0x16131lx506^error,msg="error on line 207 of \"/SourceCache/gdb/gdb-908/src/gdb/macosx/i386-macosx-nat-exec.c\" in function \"fetch_inferior_registers\": (os/kern) invalid argument (0x4)\n"
I've seen several places that claim te explain the 1st warning, but none of them seem appropriate. Nothing online claims to explain the error.
Any clues as to what these errors mean in conjunction?
ETA: I just upgraded to 10.6, so it may have started then, although I'm compiling to target 10.4...
Is this relevant? From the Xcode release notes:
Note: GCC 4.2 cannot be used with the
Mac OS X 10.4u SDK. If you want to
build targets using the 10.4u SDK on
Xcode 3.2, you must set the Compiler
Version to GCC 4.0