hi everybody,

i've added some files in my subdirectories which i'm currently working. when i tried to re-make (which i've already re-configure), it returned an error message:

make:***No rule to make target `apps/sctp_app1.cc', needed by `apps/sctp_app1.o'. Stop.

can anybody tell me what is the problem?

thank you in advance for your help..

We have no way of knowing what happened when you added the files and/or when you re-configured. What files did you add and where (and, I will ask: why)?

Assuming that you are operating "make" from the ns-2.0 directory, there was sub-directory named "apps" there. Inside that sub-directory was a file named "sctp_app1.cc". Is it still there?

In the original ns-2.0 directory, the original Makefile (generated from Makefile.in by your initial run of "configure") contains a line that says there is a target in the "apps" sub-directory named "sctp_app1.o", and there is a general rule in the Makefile that tells how to make an "anything.o" target from an "anything.cc" file. The "make" program was dutifully looking in the apps directory for a file named "sctp_app1.cc" so that it could apply the rule, and couldn't find "sctp_app1.cc". Therefore it looked for a rule to tell it how to create "sctp_app1.cc", and of course there isn't any such rule, since "sctp_app1.cc" was supposed to be in the distribution. Therefore the "make" program Stopped, as it reported.

Regards,

Dave

hi dave,

for your information, i'm working on a project of an enhancement of mobile IP. so i've to put the original files (which contains all the source codes in order to run the original) into my subdirecty (../home/myfolder/ns-allinone-2.26/ns-2.26/) and make an enhancement on that original codes. after placing those files, all I need to do is to re-configure and to re-make right? Please correct me if I'am wrong.

I have checked /apps directory and there is no single file named "sctp_app1.cc". what should I do now? do I have to create the file?..or is there any other way to solve it?..really need your help..thank you..

Are you modifying the files that are use to create the ns executable itself? I don't understand what you are doing.
The configure program uses Makefile.in to create the Makefile. If you have any new targets within the original subdirectories, or any new subdirectories that contain new targets that you want to be part of the build, then you must modify Makefile.in before you do the "configure" thing again.

If you have successfully created new object or executable files with the new stuff that you have put in, then it might be possible to run "automake" and create the new configuration information for configure and the other files. That's how packagers put stuff like this together. I really, really can't go into automake here. ("Why?" you may ask. "Well, because I don't know enough about all of the things that can go wrong to be able to work through it with you," I reply.)


Well, if the original "apps" directory didn't have "sctp_app1.c", the original build wouldn't have worked. If the original file was there and your present build directory doesn't have an apps/sctp_app1.c file then either:

1. You didn't copy it

or

2. Some subsequent operation that you performed resulted in its demise.


When I was in the Navy we used to tell people with problems like this: "The chaplain's office is just down this passageway."

Just kidding.

I can't possibly know what you did and what you didn't do when you created your new directory. (How did you copy the original files? Did you use "cp -R" from your modified directory tree or untar the original distribution or what?)

What should you do now? If that missing file is the only thing that causes the build to fail, then you could try copying the original one to its rightful place in your new build directory sub-tree. If make now complains about another file in the same directory, maybe you just didn't copy the apps directory to your new build directory. So, try it and see if you can figure out what the heck happened.

So, what to do if everything is "hosed" in some manner that doesn't seem fixable?

If your modifications were only in changing contents of certain files, then copy them somewhere else and empty out your new build directory and sub-directories. Then untar the distribution to your new directory. Then put the modified files back into their proper places.

If your modifications involved new files and/or subdirectories, then, after untarring the original distribution, you must put the new stuff inplace and put the new targets (and special rules for making them, if necessary) into Makefile.in before running configure.


Regards,

Dave