So, @veblush, the node test was broken here reporting no problem (see grpc/grpc-node#1239 - the upb submodule change broke it), which means a few build issues cropped since this happened. One of them being this:

static library binding.gyp:absl__strings__strings#target has several files with the same basename:
  escaping: deps/grpc/third_party/abseil-cpp/absl/strings/escaping.cc deps/grpc/third_party/abseil-cpp/absl/strings/internal/escaping.cc

This probably is something we want to double-file with abseil. The gist is that if you try to create a static library under macos using XCode with the same filename twice, one will get ignored or overridden by the other one, even if they come from different sub directories.

I am guessing this issue with escaping.cc isn't biting us right now because we're currently not using features from these files, but nodejs' build system is more pedantic to make sure this doesn't spread. #21639 has more details on what's going on.

Hopefully we can get abseil/abseil-cpp#605 in, to fix the next breakage on this PR.

Thank you for the report. This is interesting but I think it could be a bit out-dated warning. The warning was needed before with msvc2008 and mac make with libtool on mac and it has been considered to remove this check as no one is actively using those. Is it possible to use --no-duplicate-basename-check ?

Reference:

• --no-duplicate-basename-check
• gyp: Duplicate basenames in sources section
• Internal: GYP duplicate basename check

@veblush: if this was working, sure: nodejs/node-gyp#2026

This issue/PR has been automatically marked as stale because it has not had any update (including commits, comments, labels, milestones, etc) for 30 days. It will be closed automatically if no further update occurs in 7 day. Thank you for your contributions!