-
I'm using this project as a dependency that I'm building with Bazel. I'm using the rules_foreign_cc Creating static library librdkafka++.a
ar rcsrcsD librdkafka++.a RdKafka.o ConfImpl.o HandleImpl.o ConsumerImpl.o ProducerImpl.o KafkaConsumerImpl.o TopicImpl.o TopicPartitionImpl.o MessageImpl.o HeadersImpl.o QueueImpl.o MetadataImpl.o
ar: two different operation options specified Digging around a bit, the issue is with the ARFLAGS. The sandboxed environment that Bazel and rules_foreign_cc presents to the configure script cause the the My question is: How can I control the generation of the ARFLAGS? My attempts so far have included:
So far I'm not having much luck. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
I think your analysis is correct. Maybe we should change it so that a user-supplied ARFLAGS (such as in your case) replaces, rather than adds to, the mklove-defined ARFLAGS, but that risks doing another operation than intended. Another alternative is to remove duplicate operations from ARFLAGS, which is the actual problem here - |
Beta Was this translation helpful? Give feedback.
-
@edenhill I found a workable solution. I cribbed this solution from envoy. Basically, rules_foreign_cc allows you to specify Make targets, and with that command you can inject an environment variable.
I feel like they may be a safer way to do this, but this works for now. |
Beta Was this translation helpful? Give feedback.
@edenhill I found a workable solution. I cribbed this solution from envoy. Basically, rules_foreign_cc allows you to specify Make targets, and with that command you can inject an environment variable.
I feel like they may be a safer way to do this, but this works for now.