Here is what I would do:

cd <TOP OF TREE>
rm build-root/.bootstrap.ok
touch src/vppinfra/string.h # I just touch a random vppinfra file in case
the build needs an extra "kick in the pants"
make bootstrap
make build # or whatever is suitable for your purpose

Others will have a more standard clean up procedure but I bet this will
work.

Burt

On Mon, Oct 30, 2017 at 3:34 AM, Shachar Beiser <shacha...@mellanox.com>
wrote:

> Hi,
>
>        I have attached below the structure of the directories & files .
>
>        What is the exact command I need to use ?
>
>                      -Shachar Beiser.
>
>
>
>
>
>
>
> Compilation issue on stable/1710
>
>
>
> ./.libs/libvppcom.so: undefined reference to `unformat_init_unix_file'
>
> collect2: error: ld returned 1 exit status
>
> ./.libs/libvppcom.so: undefined reference to `unformat_init_unix_file'
>
> Makefile:5386: recipe for target 'vcl_test_client' failed
>
> make[4]: *** [vcl_test_client] Error 1
>
> make[4]: *** Waiting for unfinished jobs....
>
> collect2: error: ld returned 1 exit status
>
> Makefile:5392: recipe for target 'vcl_test_server' failed
>
> make[4]: *** [vcl_test_server] Error 1
>
> make[4]: Leaving directory '/home/ubuntu/vpp.bin/build-
> root/build-vpp-native/vpp'
>
> Makefile:7066: recipe for target 'all-recursive' failed
>
> make[3]: *** [all-recursive] Error 1
>
> make[3]: Leaving directory '/home/ubuntu/vpp.bin/build-
> root/build-vpp-native/vpp'
>
> Makefile:3595: recipe for target 'all' failed
>
> make[2]: *** [all] Error 2
>
> make[2]: Leaving directory '/home/ubuntu/vpp.bin/build-
> root/build-vpp-native/vpp'
>
> Makefile:698: recipe for target 'vpp-build' failed
>
> make[1]: *** [vpp-build] Error 2
>
> make[1]: Leaving directory '/home/ubuntu/vpp.bin/build-root'
>
> Makefile:322: recipe for target 'build-release' failed
>
> make: *** [build-release] Error 2
>
> ubuntu@ubuntu:~/vpp.bin$ echo $TOOL_INSTALL_DIR
>
>
>
> File system:
>
>
>
> ubuntu@ubuntu:~/vpp.bin$ find . -name "libvppinfra*" -print
>
> ./build-root/build-tool-native/tools/libvppinfra.la
>
> ./build-root/build-tool-native/tools/.libs/libvppinfra.lai
>
> ./build-root/build-tool-native/tools/.libs/libvppinfra.a
>
> ./build-root/build-tool-native/tools/.libs/libvppinfra.la
>
> ./build-root/build-tool-native/tools/.libs/libvppinfra.so.0.0.0
>
> ./build-root/build-tool-native/tools/.libs/libvppinfra.so
>
> ./build-root/build-tool-native/tools/.libs/libvppinfra.so.0
>
> ./build-root/install-vpp-native/vpp/lib64/libvppinfra.a
>
> ./build-root/install-vpp-native/vpp/lib64/libvppinfra.la
>
> ./build-root/install-vpp-native/vpp/lib64/libvppinfra.so.0.0.0
>
> ./build-root/install-vpp-native/vpp/lib64/libvppinfra.so
>
> ./build-root/install-vpp-native/vpp/lib64/libvppinfra.so.0
>
> ./build-root/deb/debian/vpp-lib/usr/lib/x86_64-linux-gnu/
> libvppinfra.so.0.0.0
>
> ./build-root/deb/debian/vpp-lib/usr/lib/x86_64-linux-gnu/libvppinfra.so
>
> ./build-root/deb/debian/vpp-lib/usr/lib/x86_64-linux-gnu/libvppinfra.so.0
>
> ./build-root/build-vpp-native/vpp/libvppinfra.la
>
> ./build-root/build-vpp-native/vpp/.libs/libvppinfra.lai
>
> ./build-root/build-vpp-native/vpp/.libs/libvppinfra.a
>
> ./build-root/build-vpp-native/vpp/.libs/libvppinfra.la
>
> ./build-root/build-vpp-native/vpp/.libs/libvppinfra.so.0.0.0
>
> ./build-root/build-vpp-native/vpp/.libs/libvppinfra.so
>
> ./build-root/build-vpp-native/vpp/.libs/libvppinfra.so.0
>
> ./build-root/tools/lib64/libvppinfra.a
>
> ./build-root/tools/lib64/libvppinfra.la
>
> ./build-root/tools/lib64/libvppinfra.so.0.0.0
>
> ./build-root/tools/lib64/libvppinfra.so
>
> ./build-root/tools/lib64/libvppinfra.so.0
>
>
>
> *From:* Burt Silverman [mailto:bur...@gmail.com]
> *Sent:* Monday, October 23, 2017 8:50 PM
> *To:* Shachar Beiser <shacha...@mellanox.com>
> *Cc:* vpp-dev@lists.fd.io; Shahaf Shuler <shah...@mellanox.com>
> *Subject:* Re: [vpp-dev] compilation issue on master branch latest
>
>
>
> This is triggered primarily by a bad line in build-root/Makefile
>
>
>
>     export LD_LIBRARY_PATH=$(TOOL_INSTALL_DIR)/lib64:$(TOOL_INSTALL_DIR)/lib
> ;
>
>
>
> I am hoping the build folks get some extra minutes in their schedule so I
> can discuss it with them if necessary. In the meantime, the extra cleaning
> Damjan suggests is the way to go.
>
>
>
> Basically, the build of vcl_test_server or vcl_test_client is seeing some
> outdated libvppinfra.so.0.0.0 in the directory $(TOOL_INSTALL_DIR)/lib64.
>
>
>
> Ironically, in this case "make wipe" or "make wipe-release" causes the
> problem to appear, rather than to disappear. [Most problems disappear after
> "make wipe"].
>
>
>
> You can force the problem to appear by loading a junk libvppinfra.so.0.0.0
> file in $(TOOL_INSTALL_DIR)/lib64. The build system is not supposed to be
> picking up libvppinfra.so.0.0.0 from this location.
>
>
>
> Burt
>
>
>
> On Mon, Oct 23, 2017 at 3:53 AM, Shachar Beiser <shacha...@mellanox.com>
> wrote:
>
> Hi,
>
>
>
>         I have a compilation issue on latest master branch.
>
>
>
>        -Shachar Beiser
>
>
>
>
>
> make[4]: Entering directory '/home/ubuntu/vpp.shacharbe/
> build-root/build-vpp-native/vp      p'
>
>   CC       vnet/tcp/builtin_client.lo
>
>   CC       vpp/vnet/bin_vpp-main.o
>
>   CC       vpp/app/bin_vpp-version.o
>
>   CCLD     vcl_test_server
>
>   CCLD     vcl_test_client
>
> ./.libs/libvppcom.so: undefined reference to `unformat_init_clib_file'
>
> ./.libs/libvppcom.so: undefined reference to `unformat_init_clib_file'
>
> collect2: error: ld returned 1 exit status
>
> Makefile:5536: recipe for target 'vcl_test_client' failed
>
> make[4]: *** [vcl_test_client] Error 1
>
> make[4]: *** Waiting for unfinished jobs....
>
> collect2: error: ld returned 1 exit status
>
> Makefile:5542: recipe for target 'vcl_test_server' failed
>
> make[4]: *** [vcl_test_server] Error 1
>
> make[4]: Leaving directory '/home/ubuntu/vpp.shacharbe/
> build-root/build-vpp-native/vpp      '
>
> Makefile:7268: recipe for target 'all-recursive' failed
>
> make[3]: *** [all-recursive] Error 1
>
>
> _______________________________________________
> vpp-dev mailing list
> vpp-dev@lists.fd.io
> https://lists.fd.io/mailman/listinfo/vpp-dev
> <https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.fd.io%2Fmailman%2Flistinfo%2Fvpp-dev&data=02%7C01%7Cshacharbe%40mellanox.com%7C2be136fa3a884c7205c108d51a3e8b44%7Ca652971c7d2e4d9ba6a4d149256f461b%7C0%7C0%7C636443778297203365&sdata=i615ksfYfCl5j0BGdJN4aEqed68%2BAcSxNGkjiKqDeNA%3D&reserved=0>
>
>
>
_______________________________________________
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Reply via email to