Issue running the example kafka-serdes-avro-console-producer
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- build-system
Research direction
Start by reproducing make kafka-serdes-avro-console-producer from the examples directory and inspect the link command shown in the issue. Trace the undefined RdKafka::Producer::create and RdKafka::err2str references against the listed librdkafka++ and librdkafka libraries. Done means the example links successfully with the documented build setup.
Written by the indexing model from the issue text.
Description
When I try to run the console producer getting following. Looks like some type of C++ linking issue need help to debug etc.
Error Detail
/libserdes/examples/kafka-serdes-avro-console-producer.cpp:331: undefined reference to RdKafka::Producer::create(RdKafka::Conf const*, std::string&)' /remote/vgrnd104/rachana/081222/libserdes/examples/kafka-serdes-avro-console-producer.cpp:363: undefined reference to RdKafka::err2str(RdKafka::ErrorCode)’
collect2: error: ld returned 1 exit status
make: *** [kafka-serdes-avro-console-producer] Error 1
Make Detail
/libserdes/examples % make kafka-serdes-avro-console-producer
g++ -g -O2 -fPIC -Wall -Wsign-compare -Wfloat-equal -Wpointer-arith -Wcast-align -I…/src -Wno-non-virtual-dtor --std=c++11 -I…/src -I…/src-cpp -D_GLIBCXX_USE_CXX11_ABI=0 -I…/output/include …/output/lib/libserdes.a …/output/lib/libserdes++.a …/output/lib/librdkafka++.a kafka-serdes-avro-console-producer.cpp
-o kafka-serdes-avro-console-producer …/output/lib/libserdes++.a …/output/lib/librdkafka++.a …/output/lib/libserdes.a -L…/output/lib -lrt -lpthread -lcurl -ljansson -lavrocpp -lavro -lrdkafka++ -lrdkafka
apache-kafka
- Dominant language
- C
- Stars
- 12
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from confluentinc/libserdes
-
Difficulty 3/5 Half a day Newbie friendliness 22/100
confluentinc/libserdes#68 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 15/100
confluentinc/libserdes#66 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
confluentinc/libserdes#64 ·
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
confluentinc/libserdes#63 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
confluentinc/libserdes#59 · 2 comments ·
All issues in confluentinc/libserdes
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
arduino/ArduinoCore-mbed#1126 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
security
Difficulty 1/5 Under an hour Newbie friendliness 93/100
btclib-org/btclib-secp256k1#1427 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
esmuellert/codediff.nvim#594 ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 67/100