Skip to content
TheChatArchiveThe Chat Archive
Claudeclaude-sonnet-4-20250514· AnthropicHugging Face LMArena Human Preference 140K

I think the problem is simpler. If there is a rule "/foo/bar/%.cpp.o:" and I type "make…

From a Chatbot Arena battleThe same person sent this prompt to two anonymous models at once. Compare it with DeepSeekdeepseek-v3-0324’s answer.
  1. User

    I think the problem is simpler. If there is a rule "/foo/bar/%.cpp.o:" and I type "make /foo/bar/baz.cpp.o", should I ever get the error "No rule to make target '/foo/bar/baz.cpp.o'"? The remainder of the makefile should not affect this. This is gmake 3.81 on macOS by the way. Are there some versions of make that do not accept text on both sides of % wildcards perhaps?

  2. Claude Assistant

    You're absolutely right to focus on this fundamental issue. With the rule:

    /foo/bar/%.cpp.o:
    

    Running make /foo/bar/baz.cpp.o should always match that pattern rule, regardless of what else is in the Makefile. If you're getting "No rule to make target", then something is wrong at a very basic level.

    However, GNU Make 3.81 is from 2006 and is quite old. More importantly, there are some subtle pattern matching behaviors that could be at play:

    Potential Issues with GNU Make 3.81

    1. Pattern rule matching edge cases: Very old versions of GNU Make had some quirks with pattern matching, especially when dealing with absolute paths or complex directory structures.

    2. Whitespace sensitivity: Make sure there are no trailing spaces or tabs in your pattern rule line.

    3. Character encoding issues: On macOS, there could be Unicode normalization issues if your directory names contain special characters.

    Quick Test

    Try this minimal test case to isolate the issue:

    # Minimal test
    build/paris/%.cpp.o:
    	@echo "Rule matched: building $@ from $<"
    	touch $@
    
    test:
    	@echo "Testing pattern rule..."
    

    Then run:

    mkdir -p build/paris
    make build/paris/test.cpp.o
    

    If this fails with "No rule to make target", then you've confirmed it's a fundamental issue with your Make version or environment.

    GNU Make Version Issues

    GNU Make 3.81 is extremely old (nearly 20 years). macOS ships with BSD Make by default, but if you're specifically using GNU Make 3.81, you might have installed it via an old package manager or it's a very old system.

    Recommendation: Upgrade to a modern GNU Make:

    # Install modern GNU Make via Homebrew
    brew install make
    
    # This installs as 'gmake' to avoid conflicts
    gmake --version  # Should show 4.3 or newer
    

    Or use the system's BSD Make (just make), which should handle this pattern correctly.

    Alternative Debugging

    If you can't upgrade immediately, try these variations to see what works:

    # Test 1: Relative path
    build/paris/%.cpp.o:
    	touch $@
    
    # Test 2: Simpler pattern  
    %.cpp.o:
    	touch $@
    
    # Test 3: Explicit rule (should always work)
    build/paris/champs.cpp.o:
    	touch $@
    

    The fact that you're getting "No rule to make target" for a straightforward pattern rule strongly suggests either a very old/buggy Make version or some environment issue specific to your setup.

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.