diff options
| author |   Damjan Marion <damarion@cisco.com> | 2018-09-12 14:01:10 +0200 |
|---|---|---|
| committer |   Dave Barach <openvpp@barachs.net> | 2018-09-12 16:38:59 +0000 |
| commit | 79dcbc74cd417f4caf41bc398ccba94cab7d656b (patch) | |
| tree | 043a57b2a904636093ff08b44f97172d09c36114 /docs/gettingstarted | |
| parent | 350155329c6075cef48b2d6934329a7ad75cf5c8 (diff) | |
Always use 'lib' instead of 'lib64'
It is packaging responsibility to put libs in the right place.
Use of lib64 resulted in huge amount of files with hardcoded lib64.
This patch simplifies things...
Change-Id: Iab0dea0583e480907732c5d2379eb951a00fa9e6
Signed-off-by: Damjan Marion <damarion@cisco.com>
Diffstat (limited to 'docs/gettingstarted')
| -rw-r--r-- | docs/gettingstarted/developers/gdb_examples.rst | 2 | ||||
| -rw-r--r-- | docs/gettingstarted/progressivevpp/runningvpp.rst | 2 | ||||
| -rw-r--r-- | docs/gettingstarted/users/configuring/startup.rst | 4 |
3 files changed, 4 insertions, 4 deletions
diff --git a/docs/gettingstarted/developers/gdb_examples.rst b/docs/gettingstarted/developers/gdb_examples.rst index 8a0fb33e2a8..71340dabcd0 100644 --- a/docs/gettingstarted/developers/gdb_examples.rst +++ b/docs/gettingstarted/developers/gdb_examples.rst @@ -18,7 +18,7 @@ Once at the gdb prompt, VPP can be started by running the following commands: Starting program: /scratch/vpp-master/build-root/install-vpp_debug-native/vpp/bin/vpp -c /etc/vpp/startup.conf [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". - vlib_plugin_early_init:361: plugin path /scratch/vpp-master/build-root/install-vpp_debug-native/vpp/lib/vpp_plugins:/scratch/vpp-master/build-root/install-vpp_debug-native/vpp/lib64/vpp_plugins + vlib_plugin_early_init:361: plugin path /scratch/vpp-master/build-root/install-vpp_debug-native/vpp/lib/vpp_plugins:/scratch/vpp-master/build-root/install-vpp_debug-native/vpp/lib/vpp_plugins .... Backtrace diff --git a/docs/gettingstarted/progressivevpp/runningvpp.rst b/docs/gettingstarted/progressivevpp/runningvpp.rst index ff20064b5eb..19d2f4e9ede 100644 --- a/docs/gettingstarted/progressivevpp/runningvpp.rst +++ b/docs/gettingstarted/progressivevpp/runningvpp.rst @@ -20,7 +20,7 @@ Using the files we created in setup we will start VPP. .. code-block:: console $ sudo /usr/bin/vpp -c startup1.conf - vlib_plugin_early_init:361: plugin path /usr/lib/vpp_plugins:/usr/lib64/vpp_plugins + vlib_plugin_early_init:361: plugin path /usr/lib/vpp_plugins:/usr/lib/vpp_plugins load_one_plugin:189: Loaded plugin: abf_plugin.so (ACL based Forwarding) load_one_plugin:189: Loaded plugin: acl_plugin.so (Access Control Lists) load_one_plugin:189: Loaded plugin: avf_plugin.so (Intel Adaptive Virtual Function (AVF) Device Plugin) diff --git a/docs/gettingstarted/users/configuring/startup.rst b/docs/gettingstarted/users/configuring/startup.rst index 0bc6ca4ae8a..77f12b24e3e 100644 --- a/docs/gettingstarted/users/configuring/startup.rst +++ b/docs/gettingstarted/users/configuring/startup.rst @@ -1225,7 +1225,7 @@ only the plugins that are desired. * **path <path>** Adjust the plugin path depending on where the VPP plugins are installed. - **Example:** path /home/bms/vpp/build-root/install-vpp-native/vpp/lib64/vpp_plugins + **Example:** path /home/bms/vpp/build-root/install-vpp-native/vpp/lib/vpp_plugins * **name-filter <filter-name>** TBD @@ -1277,7 +1277,7 @@ Alternate syntax to choose plugin path. Plugin_path configuration controls the set of directories searched for vlib plugins. Supply a colon-separated list of (absolute) directory names: plugin_path dir1:dir2:...:dirN - **Example:** plugin_path /home/bms/vpp/build-root/install-vpp-native/vpp/lib64/vpp_plugins + **Example:** plugin_path /home/bms/vpp/build-root/install-vpp-native/vpp/lib/vpp_plugins .. _punt: |