> Unexpected End
> Make Unexpected End Of Line Seen Solaris
Make Unexpected End Of Line Seen Solaris
Also, I am not 100% sure that this is the correct code for the makefile (specifically the assembling of my support.s file, and the linking of both files). Why does Wikipedia list an improper pronunciation of Esperanto? Not sure whether there could be any difference. Do let me know if you need anything else. http://fullflash.net/unexpected-end/unexpected-end-ruby.html
All rights reserved.Unauthorized reproduction or linking forbidden without expressed written permission. Report bugs to <[hidden email]>.--------------------- The make file that we use is =============================### Makefile# Author: Merlin Hughes## Copyright: Copyright 1998-2000 Baltimore Technologies, plc.## Summary: Master Makefile.## # product share|improve this answer answered May 5 '10 at 22:47 Diavolche 11 @Diavolche: Only the beginning of Line 219 in the code excerpt has a tab. –Winston C. Browse other questions tagged makefile solaris gnu-make or ask your own question. click to read more
Make Unexpected End Of Line Seen Solaris
Why do the Sparkfun and Adafruit Eagle libraries use smaller footprints than the manufacturer's recommended land pattern? John Red Flag This Post Please let us know here why this post is inappropriate. What's going on? Join UsClose Login with LinkedIN Or Log In Locally Email Password Remember Me Forgot Password?Register ENGINEERING.com Eng-Tips Forums Tek-Tips Forums Search Posts Find A Forum Thread Number Find An Expert
reply via email to [Prev in Thread] Current Thread [Next in Thread] RE: 'Unexpected end of line seen' error while building CSSL using GNU make., Swaroop Sugunan<= RE: 'Unexpected end of Secondly, what are you expectng $^ to expand to? –James McPherson Feb 12 '14 at 0:47 Thanks for catching that. Do I have to delete lambdas? I may also give inefficient code or introduce some problems to discourage copy/paste coding.
It's impossible for any of the commands you> ran (configure, etc.) to add anything to your PATH.> > > echo $PATH gives the following> > > > bash-3.00# echo $PATH> > I had this issue but I found out the command was not properly tabbed in and that is why I was running into this error. Thanks and Regards, Swaroop.Get the new Windows Live Messenger! That line doesn't look like a rule, but you've tried adding tabs anyway, to no avail: > If we replace the := with a = then the line number keeps going
Cancel Red Flag SubmittedThank you for helping keep Tek-Tips Forums free from inappropriate posts.The Tek-Tips staff will check this out and take appropriate action. You can fix it in Notepad++: edit->EOL conversion->Unix (or Windows or Old Mac) or you can reenter the newline characters manually on the machine on which you're compiling. Try our newsletter Sign up for our newsletter and get our top new questions delivered to your inbox (see an example). share|improve this answer edited Feb 12 '14 at 2:47 answered Feb 12 '14 at 0:20 James McPherson 72338 That's what I get for copying from a powerpoint and not
- Smith <[hidden email]> Find some GNU make tips at: http://www.gnu.org http://make.paulandlesley.org"Please remain calm...I may be mad, but
- You also have what appears to be incorrect compiler flag syntax - there shouldn't be any whitespace between - and o to form the output arg -o [email protected]
- Browse other questions tagged c makefile or ask your own question.
- I do think the original poster's problem might be incompatible newline expressions. –Ezry May 22 '14 at 20:26 add a comment| Your Answer draft saved draft discarded Sign up or
- As @jia103 alluded to, you have a spurious $ in your $(EXE) rule.
- Fortunately, the make(1s) manpage is reasonably well written.
- We were trying to build from "bash" and were getting the error mentioned below.
Makefile Unexpected End Of Line Seen Solaris
Thanks folks! –user2731040 Nov 17 '14 at 22:05 add a comment| active oldest votes Know someone who can answer? weblink Talk With Other Members Be Notified Of ResponsesTo Your Posts Keyword Search One-Click Access To YourFavorite Forums Automated SignaturesOn Your Posts Best Of All, It's Free! Here is the makefile: proj09.exe: proj09.driver.o proj09.support.o gcc -Wall proj09.driver.o proj09.support.o -o proj09.exe proj09.driver.o: proj09.driver.c /user/cse320/Projects/project09.support.h gcc -Wall -c proj09.driver.c /user/cse320/Projects/project09.support.h proj09.support.o: proj09.support.s gcc -Wall proj09.support.s When I try to make I know it well, since I work on the Solaris kernel and that's the tool we use.
I hope you have written your makefile in GNU style. more stack exchange communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed Why cast an A-lister for Groot? navigate here Namely, CSSL.
In this gmake is GNU style make command, and make is solaris style make command. Otherwise how will the function declarations and such be expressed in the resulting object file? –Serpent_wooer Nov 23 '12 at 16:07 No, you're supposed to #include the header file. That is certainly possible. –Etan Reisner Nov 13 '14 at 20:00 "fatal error in reader" is something that Solaris make can output, so it looks like Vulcan might be
If we replace all the := with =, then it ends > with "nothing to do with product".
I stripped out the comments and a bunch of path declarations and the like. How would a person see with an adjustable cross-shaped pupil? But the makefiles in your package DO rely on GNU make syntax, so you need to be sure GNU make is invoked. > However, one thing is which I noticed is Dealing with a nasty recruiter Player claims their wizard character knows everything (from books).
Free forum by Nabble Edit this page Developer Network Developer Network Developer :CreateViewProfileText: Sign in MSDN subscriptions Get tools Downloads Visual Studio MSDN subscription access SDKs Trial software Free downloads Office Close Reply To This Thread Posting in the Tek-Tips forums is a member-only feature. Again, this is a shell issue (your PATH is not being maintained in some situations), not a make issue. http://fullflash.net/unexpected-end/unexpected-end-of-input-json.html So I think for that particular build statement uses the gmake itself.
Also there shouldn't be any spaces after the command. Not the answer you're looking for? Again, if you cut and pasted the error messages this would have been clear immediately, and saved a lot of confusion. –MadScientist Feb 12 '14 at 0:53 Ok, exact There can be any> number of reasons this is not working, and your description of what> happens is nowhere near detailed enough for us to even guess which one> it might