Showing posts from March, 2014

[Cross-Compile] What's the difference of `./configure` option `--build`, `--host` and `--target`?

When using ./configure especially in cross-compiling purpose, I kind of confuse about the option --build and --host so that the following content is what I found on searching:

some remarks on specifying --host=<host>, --target=<target> and --build=<build
# kindly provided by Keith Marshall:
# 1) build
# this is *always* the platform on which you are running the build
# process; since we are building on Linux, this is unequivocally going to
# specify `linux', with the canonical form being `i686-pc-linux-gnu'.
# 2) host
# this is a tricky one: it specifies the platform on which whatever we
# are building is going to be run; for the cross-compiler itself, that's
# also `i686-pc-linux-gnu', but when we get to the stage of building the
# runtime support libraries to go with that cross-compiler, they must
# contain code which will run on the `i686-pc-mingw32' host, so the `host'
# specification should change to this, for the `runtime' and `w32api…

[NETCONF] The summary of NETCONF Content

The following content is about the summary of the NET-CONF web site: Initiation For Clients <?xml version="1.0" encoding="UTF-8"?> <hello xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <capabilities> <capability>urn:ietf:params:netconf:base:1.0</capability> </capabilities> </hello>]]>]]> Protocol Capabilities <capability> urn:ietf:params:netconf:capability:writable-running:1.0 </capability>
<capability>urn:ietf:params:netconf:base:1.0</capability> Standard Capabilities :candidate :confirmed-commit :interleave :notification :partial-lock :rollback-on-error :startup :url :validate :writable-running :xpath Configuration Databases<running/> <candidate/> <startup/> Protocol OperationsOnce a NETCONF session is established, the client knows which capabilities the server supports. T…