Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7580567
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 30, 20262026-05-30T17:57:02+00:00 2026-05-30T17:57:02+00:00

I have the following makefile which is a slight modification on others that I

  • 0

I have the following makefile which is a slight modification on others that I have used in the past. There is an odd issue though with my variable ${CXXOPTS} not being used in the .c.o makefile rule. When I execute the makefile, this is what is executed g++ -c -o SeqPrep2.o SeqPrep2.cpp when I expect this to be executed: g++ -Iseqan-03-02-2012 -c -o SeqPrep2.o SeqPrep2.cpp. (Edit: I solved the problem but see my updated question below about why this makefile worked at all in the first place)

L=-lm -lz
SEQANINC=seqan-03-02-2012
DESTDIR=$(HOME)/
BINDIR=bin
CXXOPTS=-I${SEQANINC}
CXX=g++
A=SeqPrep2
USEROPTS=
O=$(patsubst %.cpp,%.o,$(wildcard *.cpp))
SOURCES=$(wildcard *.cpp)

all: ${A} ${O} ${SOURCES}

install: ${O} ${MYLIBS} ${SOURCES}
    ${CXX} ${USEROPTS} -o ${DESTDIR}${BINDIR}/${A} ${O} ${L}

${A}: ${O} ${MYLIBS} ${SOURCES}
    ${CXX} ${USEROPTS} -o ${A} ${O} ${L}

clean::
    rm -f ${A} ${O}

.c.o:
    ${CXX} ${CXXOPTS} ${USEROPTS} -c  $< -o $@

check-syntax:
    ${CXX} ${CXXOPTS} ${USEROPTS} -c -o .nul -S ${CHK_SOURCES}

UPDATE:

I changed .c.o to .cpp.o. Is this a case of gnu make guessing that when I asked for a .o file in one of my rules, that it should make it just by running g++ -c -o SeqPrep2.o SeqPrep2.cpp even though I didn’t tell it to do that? I guess that is my new question, why did the above makefile work at all, and why did it have the odd behavior I observed. One thing to note is that even though it didn’t come though in the formatting, there is a lot of white space between the g++ and the -c, kind of like it was trying to put in my variables, but it didn’t. That is partially what originally lead me to believe that it was seeing my rule at all, even though it seems like it didn’t now. Thanks for helping me understand how this stuff works.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-30T17:57:03+00:00Added an answer on May 30, 2026 at 5:57 pm

    You’ve got the rule .c.o but you’re compiling cpp files, when I use .cpp.o: it works great! With files: me.cpp us.cpp you.cpp

    I get:

    Building file me.cpp
    g++ -Iseqan-03-02-2012  -c  me.cpp -o me.o
    Building file us.cpp
    g++ -Iseqan-03-02-2012  -c  us.cpp -o us.o
    Building file you.cpp
    g++ -Iseqan-03-02-2012  -c  you.cpp -o you.o
    g++  -o SeqPrep2 me.o us.o you.o -lm -lz
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

In a makefile, I have the following line: helper.cpp: dtds.h Which ensures that helper.cpp
I have used -Wall -Werror in my Makefile but I want to disable following
I have a makefile (provided by third party) which gives the following error Makefile:108:
I have the following makefile that I use to build a program (a kernel,
In my makefile I have the following target, which compiles text/HTML resources into unsigned
I have the following makefile for my project, and I'd like to configure it
Utility: NMake Platform : Windows 7 I have the following Makefile FILE = $(shell)
I have the following implicit rule in a makefile: a1 b1: %: %.o On
I have the following PHONY target in Makefile install: echo /usr/bin/shelldecrypt must be writable
I'm creating a Makefile for a project. I have the following structure of Makefiles:

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.