Thank you, Tricia. As a workaround I added the following to bottom of the
WORKSPACE file at the root of the protobuf-25.3 directory:

local_repository(name = "com_google_protobuf", path = ".")

Everything then built fine and seems to be functional.

On Tue, Mar 5, 2024 at 4:43 AM 'Tricia Decker' via Protocol Buffers <
[email protected]> wrote:

> Hi Rick,
>
> There's an open issue for the same
> https://github.com/protocolbuffers/protobuf/issues/15615 in case you
> haven't seen it.
>
> Tricia
>
> On Monday, March 4, 2024 at 7:47:25 AM UTC-8 Rick Genter wrote:
>
>> I'm following the directions at
>> https://github.com/protocolbuffers/protobuf/blob/main/src/README.md to
>> try to build protobuf 25.3.
>>
>> I have bazel 7.0.2 installed.
>>
>> I downloaded protobuf-25.3.tar.gz, then gunzip'd and untar'd it.
>> I then cd'd to protobuf-25.3 and did
>>
>> $ bazel build :protoc
>>
>> That worked.
>>
>> I then tried
>>
>> $ bazel build :protobuf
>>
>> and get
>>
>> ERROR: no such package '@@com_google_protobuf//': The repository
>> '@@com_google_protobuf' could not be resolved: Repository
>> '@@com_google_protobuf' is not defined
>>
>> How do I fix this?
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Protocol Buffers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/protobuf/2cdb9d4f-2f4e-438b-a128-561328a33506n%40googlegroups.com
> <https://groups.google.com/d/msgid/protobuf/2cdb9d4f-2f4e-438b-a128-561328a33506n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>


-- 
Rick Genter
[email protected]

-- 
You received this message because you are subscribed to the Google Groups 
"Protocol Buffers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/protobuf/CADie1rzG72X-xvov6%3DZCydTwiRtB4WxbQSBt3UrxDH4qUghPvQ%40mail.gmail.com.

Reply via email to