search for: cc_plugin_cflags

...flags from when -nbdkit was itself compiled from source are used. To see what those -were you can do: +flags are used. If not set, you can hardcode the defaults for C<CC> +and C<CFLAGS> at the time nbdkit is compiled from source by +configuring with C<CC_PLUGIN_CC=...> and C<CC_PLUGIN_CFLAGS=...>, +otherwise, the configuration for compiling nbdkit itself is used +(C<EXTRA_CFLAGS> can only be set from the command line when starting +the cc plugin). To see what those were you can do: $ nbdkit cc --dump-plugin ... diff --git a/configure.ac b/configure.ac index afc5ddab..e5e...

...dkit was itself compiled from source are used. To see what those > -were you can do: > +flags are used. If not set, you can hardcode the defaults for C<CC> > +and C<CFLAGS> at the time nbdkit is compiled from source by > +configuring with C<CC_PLUGIN_CC=...> and C<CC_PLUGIN_CFLAGS=...>, > +otherwise, the configuration for compiling nbdkit itself is used > +(C<EXTRA_CFLAGS> can only be set from the command line when starting > +the cc plugin). To see what those were you can do: > > $ nbdkit cc --dump-plugin > ... Widening the context, .....