out_stdout: new STDOUT Output Plugin.

[pandax381]

I implemented a new STDOUT Output Plugin.
I hope that it will assist debugging.

$ ./fluent-bit -i cpu -o stdout
Fluent-Bit v0.1.0
Copyright (C) Treasure Data

[2015/06/02 18:32:54] [ info] starting engine
[0] {"time"=>1433237575, "cpu"=>0.000000}
[1] {"time"=>1433237576, "cpu"=>0.000000}
[2] {"time"=>1433237577, "cpu"=>0.000000}
[3] {"time"=>1433237578, "cpu"=>0.000000}
[2015/06/02 18:32:59] [ info] Flush buf 96 bytes
[0] {"time"=>1433237579, "cpu"=>0.000000}
[1] {"time"=>1433237580, "cpu"=>0.000000}
[2] {"time"=>1433237581, "cpu"=>0.000000}
[3] {"time"=>1433237582, "cpu"=>0.000000}
[4] {"time"=>1433237583, "cpu"=>0.000000}
[2015/06/02 18:33:04] [ info] Flush buf 120 bytes
...

Note: An error has occurred that "libmsgpack.a is not a PIC format" in the process of generating a shared library of fluent-bit. So, I added the code to add the -fPIC option to CMakeLists.txt of msgpack.

Scanning dependencies of target fluent-bit-shared
[ 81%] Building C object src/CMakeFiles/fluent-bit-shared.dir/flb_pack.c.o
[ 84%] Building C object src/CMakeFiles/fluent-bit-shared.dir/flb_input.c.o
[ 87%] Building C object src/CMakeFiles/fluent-bit-shared.dir/flb_output.c.o
[ 90%] Building C object src/CMakeFiles/fluent-bit-shared.dir/flb_config.c.o
[ 93%] Building C object src/CMakeFiles/fluent-bit-shared.dir/flb_network.c.o
[ 96%] Building C object src/CMakeFiles/fluent-bit-shared.dir/flb_utils.c.o
[100%] Building C object src/CMakeFiles/fluent-bit-shared.dir/flb_engine.c.o
Linking C shared library ../library/libfluent-bit.so
/usr/bin/ld: ../library/libmsgpack.a(unpack.c.o): relocation R_X86_64_32S against `.rodata' can not be used when making a shared object; recompile with -fPIC
../library/libmsgpack.a: could not read symbols: Bad value
collect2: error: ld returned 1 exit status
make[2]: *** [library/libfluent-bit.so] Error 1
make[1]: *** [src/CMakeFiles/fluent-bit-shared.dir/all] Error 2
make: *** [all] Error 2

Signed-off-by: Masaya YAMAMOTO [email protected]

[edsiper]

thanks!

[edsiper]

would you please check the following issue ?

#6

[pandax381]

Sorry, It's my mistake.
The cause of this problem was in in_mem plugin.
I will pull request to fix the problem urgently.