[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: no rule to make asm targets

From: Ralf Wildenhues
Subject: Re: no rule to make asm targets
Date: Tue, 5 Dec 2006 07:32:34 +0100
User-agent: Mutt/1.5.13 (2006-08-11)

* Jari Strand wrote on Tue, Dec 05, 2006 at 04:03:01AM CET:
> >From: Ralf Wildenhues <address@hidden>
> >
> >Please keep the mailing list in Cc:.  Thanks.
> I am sorry because I don't know what Cc means?

It means that, when you reply, you should also send a copy of the
message to the automake mailing list.  That way, everyone can look
at the discussion, help, learn, and I can find old messages easily.

> >* Jari Strand wrote on Mon, Dec 04, 2006 at 02:09:10PM CET:

> >> Are you saying that there should be no identation after the
> >> .asm.o: line?
> >
> >No.  The error you made was the doubled period.  Instead of writing
> >this:
> >..asm.o:

> >You should be writing this:
> >.asm.o:

> I see thank you, that was actually just a typo, it was correctly typed in 
> the


> >SUFFIXES = .asm .o
> >
> >This helps automake detect the list of suffixes; it will then set it
> >correctly for make.
> Alright I have put that SUFFICES line in but it did not help.

(I assume that this is yet another typo, right?  SUFFIXES vs. SUFFICES.)

> I wonder what is wrong and it bugs me that all of the .o files generate are 
> name like buildName-fileName.o instead of just filename.o . It probably 
> doesnt matter but I thought that I should ask at the same time if it's 
> possible to set the output location of the generated .o files?

Ahh.  Now we're getting closer.  You have per-target compilation flags,
right?  Then an inference rule won't do.  Please post your,
that may help pointing out ways out.

Generally, you could
- avoid per-target flags here to avoid the renamed object files, or
- write manual rules for all those objects, or
- write the target dependencies on the objects yourself, to control
  the object file names, or
- use Automake 1.10, and just use its builtin support for assembly
  (but then your source files need to be named *.s/*.S, and you need
  CCAS/CCASFLAGS/AM_CCASFLAGS, and the AM_PROG_AS macro; see the manual)

Hope that helps.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]