Makefile & "make" builds successfully but no executable is generated

Clang Frontend
#1

Hello everyone,

When I execute the cmd “make” the build is successful. However, the executable is NOT created/generated. Am I doing something wrong?

Below is my makefile in my example directory which is located in:
static_analysis/build/release/tools/clang/tools/example

which contains the Example.cpp file I want to compile

Makefile:

CLANG_LEVEL:= …/…

TOOLNAME = example #the name of tool’s executable

SOURCES := Example.cpp #the Clang source files you want to compile

include $(CLANG_LEVEL)/…/…/Makefile.config

LINK_COMPONENTS := $(TARGETS_TO_BUILD) asmparser bitreader support mc option

USEDLIBS = clangFrontend.a clangSerialization.a clangDriver.a \

clangTooling.a clangParse.a clangSema.a
clangAnalysis.a clangRewriteFrontend.a clangRewriteCore.a
clangEdit.a clangAST.a clangLex.a clangBasic.a
include $(CLANG_LEVEL)/Makefile

Any help would be greatly appreciated!

#2

Hello everyone,

When I execute the cmd "make" the build is successful. However, the
executable is NOT created/generated. Am I doing something wrong?

Below is my makefile in my example directory which is located in:
static_analysis/build/release/tools/clang/tools/example

which contains the Example.cpp file I want to compile

Makefile:

CLANG_LEVEL:= ../..

TOOLNAME= example #the name of tool's executable

SOURCES:= Example.cpp #the Clang source files you want to compile

include$(CLANG_LEVEL)/../../Makefile.config

LINK_COMPONENTS:= $(TARGETS_TO_BUILD)asmparser bitreader support mc option

USEDLIBS= clangFrontend.a clangSerialization.a clangDriver.a \
clangTooling.a clangParse.a clangSema.a \
clangAnalysis.a clangRewriteFrontend.a clangRewriteCore.a \
clangEdit.a clangAST.a clangLex.a clangBasic.a
include$(CLANG_LEVEL)/Makefile

Any help would be greatly appreciated!

Did you tell clang/tools/Makefile about your new directory?

Jon

#3

Hi Jonathan,

the clang/tools/Makefile seems to be autogenerated by cmake and has a
comment that says not to modify.

The one in src, not the one in the build directory.

Also, please stop replying only to me in your messages... If you don't include the list, then nobody else will see your replies, which will give them less information to help solve your problem.

#4

Also, please stop replying only to me in your messages... If you don't
include the list, then nobody else will see your replies, which will
give them less information to help solve your problem.

Let me point out that the way the lists are currently set up, many
mail clients won't include the list address in a "reply all".
This is an ongoing problem that will trip up every newcomer, and
many of us who aren't.
--paulr

#5

Apologies, just started using this mailing list and new to LLVM. I will make sure to do that in future posts.

Best Regards,

Omid Ghenatnevi

#6

> Also, please stop replying only to me in your messages... If you don't
> include the list, then nobody else will see your replies, which will
> give them less information to help solve your problem.

Let me point out that the way the lists are currently set up, many
mail clients won't include the list address in a "reply all".
This is an ongoing problem that will trip up every newcomer, and

many of us who aren't.

Really? I've not seen many replies going to me and not the mailing list,
only a handful - I'd expect this to be more pervasive if it was a software
problem, no?

Do you know what the specific problem is with the headers in the email
and/or which mail clients have problems with this?

(probably worth emailing Tanya and/or filing a bug)

- Dave

#7

I persistently have this problem with Outlook. I don’t know whether other mail clients are affected but I’ve seen other people mention it on one or another of our lists. I am clueless about mail headers. Pretty sure I have alerted the list manager(s) but can do so again.

–paulr

#8

I have this exact same problem with outlook consistently. I have to add back cfe-dev@lists.llvm.org or llvm-dev@lists.llvm.org

always in order to truly reply to all.

Kevin

#9

+Tanya

Just in case this hasn’t come up enough/needs to be bumped, this seems like a significant quality-of-life issue for some community members. Presumably happened when the mailing lists switched over to llvm.org

  • Dave
#10

+Tanya

Just in case this hasn’t come up enough/needs to be bumped, this seems like a significant quality-of-life issue for some community members. Presumably happened when the mailing lists switched over to llvm.org

I believe it has to do with the change to handle DMARC.
http://wiki.list.org/DEV/DMARC

Since the mailing list move, mailman now rewrites/munges the from header for all mailing lists (why you see the via).

I am only aware of issues with Outlook in the reply to all.

I’m not sure of the right way to fix this so that everyone is happy. We need to handle DMARC or mail will be rejected by various email servers (Yahoo, Google and others I don’t even know about), but I fully realize how annoying the dropping of the list from reply-to-all is.

I’m open to any suggestions on how to resolve this as I want the lists to be functional to all.

Thanks,
Tanya

#11

Are you using Outlook 2010 by any chance? I investigated it shortly after the move to the new mailing list and it seemed everyone having trouble was using more-or-less the same version.

Here’s the information I gave Tanya at the time:

I’ve managed to reproduce the behaviour off-list and it seems that Outlook 2010 isn’t handling the

Reply-To header properly. I’m finding that it is eliminating duplicated recipients before replacing the

From value with the Reply-To. As a result, the Reply-To removes both instances of the list (from From

and CC) rather than just one (from From) and replaces them with the original sender (in Reply-To).

Below the ‘—’ are the headers that reproduce the problem for me. The list is included if I either remove Reply-To, or change the address in From so that it differs from the one in CC.

Hope this helps find a fix. Let me know if you need more information.

CC: “list@localhost” list@localhost

Content-Type: text/plain; charset=“utf-8”

Delivered-To: list@localhost

Errors-To: list-bounces@localhost

From: Daniel Sanders via list list@localhost

MIME-Version: 1.0

Reply-To: The Original Sender Daniel.Sanders@localhost

Return-Path: list-bounces@localhost

Sender: list list-bounces@localhost

Subject: Re: [list] Test Email - Apologies for the noise

To: Alan Sample alan.sample@localhost

Unfortunately, we didn’t find a fix.

#12

Yes, I am using Outlook 2010, version 14.0.7162.5000

Do you know whether the problem is fixed in Outlook 2013?

Kevin Smith

#13

Unfortunately I don’t have a way to test Outlook 2013 but Outlook Web Access works properly.

#14

I just installed Outlook 2013. It has the same (bad) behavior that Outlook 2010 has, when replying to all with cfe-dev or llvm-dev in the cc line, it doesn’t include

those addresses on the cc line of the new message.

Kevin Smith

#15

Hi

Can i get the loop in a Cfg? Like a list of BBs that belong to a loop.

Best Regards!
Eric Lew

Sent using CloudMagic Email

#16

You could use BlockID to record the path in CFG you have traveled.
First, get the Terminator of current BB to judge whether this is a loop branch BB,(Such as ForStmt or WhileStmt in Terminator.getStmt() ).
Then from current BB, you travel its successors and record its BlockID.
and when there is a loop in the traveled BBs’ ID, you can know that you get an loop.