Forward is not defined

in Help Center
Hi.
I'm stuck with forward ( I guess ) declarations not being compiled. Please, have a look at the following output:
../../../../../cpp/bin/slice2cs --output-dir generated -I. TestAMD.ice
/tmp/zrb/Ice-3.5b/cs/test/Ice/slicing/objects/TestAMD.ice:153: `Forward' is not defined
make[4]: *** [generated/TestAMD.cs] Error 1
Could you please share your thoughts on this.
Regards,
Dmitry N. Medvedev
I'm stuck with forward ( I guess ) declarations not being compiled. Please, have a look at the following output:
../../../../../cpp/bin/slice2cs --output-dir generated -I. TestAMD.ice
/tmp/zrb/Ice-3.5b/cs/test/Ice/slicing/objects/TestAMD.ice:153: `Forward' is not defined
make[4]: *** [generated/TestAMD.cs] Error 1
Could you please share your thoughts on this.
Regards,
Dmitry N. Medvedev
0
Comments
Forward is forwarded declared in TestAMD.ice:
Did you build mcpp yourself and did you apply the required patches? The patches are included in the 3rd party source archive available on our web site here.
Cheers,
Benoit.
Thank you, Benoit for quick response.
I actually did not. My fault, sorry.
Now, python for Ice stopped with this:
I have downloaded and build python 3.3 from sources.
I have compiled Ice 3.5b from sources.
I have also created symlink /opt/Ice-3.5b/lib64 to /opt/Ice-3.5b/lib.
I have exported LD_LIBRARY_PATH containing the /opt/Ice-3.5b/lib64.
OS: Debian Squeeze x64 ( yes, I know it's unsupported but I like it, sorry for this )
I'm building 3.5.1 source on Amazon Linux. Third-party pre-reqs, cpp and py code built fine. I applied mcpp patch:
Py testing failed later:
Fixed by adding to top of test/Ice/slicing/objects/TestAMD.ice and restarting tests.
I also experienced the same lib path failure as Dmitry but in my case it was fixed by symlinking lib to lib64.
David Hinson
It sounds like the libSlice library doesn't include the fix for mcpp (removing the comment line 69 in TestAMD.ice should also workaround the problem... a bug in mcpp). Did you rebuild mcpp after applying the patch and can you ensure that libSlice was correctly linked with your libmcpp build?
Note that we also provide binaries for Amazon Linux on our download page.
Cheers,
Benoit.
I found the root of the problem on my end. libmcpp 2.7.2 had already been installed as a yum dependency of a different project into /usr/lib64. Since the Ice third party build puts it in /usr/local by default the patched lib was being eclipsed by the one in /usr/lib64. I yum removed libmcpp, cleaned and rebuilt everything with mcpp additionally configured with --prefix=/usr, and backed out the change I had made to test/Ice/slicing/objects/TestAMD.ice and then py tested ok.
I appreciate your Amazon Linux binaries and was tempted to use them but I'm a control freak when it comes to third party code even when it's punishing. Ice is actually a joy to build compared to many other large products.
Thanks for your help,
David Hinson