search

ARudik / phc

Automatically exported from code.google.com/p/phc
0 stars 0 forks source link

Can't build the current version #102

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
I'm using boost 1.34.1, and phc2.0.1

When compiling I got error with method: PHP::set_ini_entry(string, string)
which I removed (dup of declared PHP::set_ini_entry(String *, String *)) in
embed.cpp.

Then while linking I got errors:
phc.o: In function `initialize_ini_entries()':
src/phc.cpp:391: undefined reference to `PHP::set_ini_entry(String*, String*)'
./.libs/libphc.so: undefined reference to `PHP::get_altered_ini_entries()'
./.libs/libphc.so: undefined reference to `PHP::get_ini_entry(String*)'

However, objdump -S libphc.so | grep "set_ini_entry" returns no output.
Looking at the code, embed.cpp contains the said method in a #if HAVE_EMBED
section, which I haven't accepted in the configure.

I've moved the code out of #if/#else/#endif, and duplicate the
set_ini_entries to do nothing except caching the key, in the #else section.
Similarly, I've duplicated the get_ini_entry() method to return 0 in the
#else section.

With this change I could compile & link the code.

Original issue reported on code.google.com by sandrine...@gmail.com on 24 Jan 2009 at 3:01

GoogleCodeExporter commented 9 years ago 
This occurs because phc was built without the PHP embed SAPI. We don't test this
configuration, but we support it, so it should be tested more.

Its a simple fix, as sandrine.care points out. I'm testing now.

Original comment by paul.biggar on 24 Jan 2009 at 3:14

GoogleCodeExporter commented 9 years ago 
sandrine.care,

I believe I have fixed this in revision 2303 in the 0.2.0 branch. Can you do a
checkout from http://phc.googlecode.com/svn/branches/0.2.0, and confirm that it 
works
for you?

Original comment by paul.biggar on 24 Jan 2009 at 4:58

GoogleCodeExporter commented 9 years ago 
It does indeed. Thanks.

Original comment by sandrine...@gmail.com on 26 Jan 2009 at 9:20

GoogleCodeExporter commented 9 years ago 
We'll make a new minor release with this change soon (possibly wait for issue 
103 to
be resolved).

Original comment by paul.biggar on 27 Jan 2009 at 6:53