From: William P. S. I. <bil...@xp...> - 2011-02-17 22:10:32
|
Well I installed the native SDK and then tried both "Hello World" examples . I'm not much of a C++ programmer but here's what I got: The new "Hello World": Saved as 'hellothere.cpp' #include using namespace std; int main() { cout << "Gumstix can natively compile C++" << endl; return 0; } The Result: root@overo:~/temp# g++ -o hello hellothere.cpp hellothere.cpp:1:10: error: #include expects "FILENAME" or <FILENAME> hellothere.cpp: In function 'int main()': hellothere.cpp:5: error: 'cout' was not declared in this scope hellothere.cpp:5: error: 'endl' was not declared in this scope ---------------------------------------------------------------------------- ------------------------------------ The Old "Hello World": Makefile: hello: hello.c ${CC} ${CFLAGS} ${LDFLAGS} -o hello hello.c The Old "Hello World" saved as Hello.c #include "stdio.h" main(){ printf ("Hello Out There"); } The Result: root@overo:~/temp# make hello.c makefile:3: *** missing separator. Stop. ---------------------------------------------------------------------------- ---------------------------------------- Any ideas ?? Thanks . "People sleep peaceably in their beds at night only because rough men stand ready to do violence on their behalf." - George Orwell |
From: Pettinato, J. <Jim...@fm...> - 2011-02-17 22:52:45
|
Somehow your source file lost the "stdio.h" file reference in the #include statement. From: William Pretty Security Inc [mailto:bil...@xp...] Sent: Thursday, February 17, 2011 5:10 PM To: 'General mailing list for gumstix users.' Subject: [Gumstix-users] Hello World Tutorial Problems :( Well I installed the native SDK and then tried both "Hello World" examples ... I'm not much of a C++ programmer but here's what I got: The new "Hello World": Saved as 'hellothere.cpp' #include using namespace std; int main() { cout << "Gumstix can natively compile C++" << endl; return 0; } The Result: root@overo:~/temp# g++ -o hello hellothere.cpp hellothere.cpp:1:10: error: #include expects "FILENAME" or <FILENAME> hellothere.cpp: In function 'int main()': hellothere.cpp:5: error: 'cout' was not declared in this scope hellothere.cpp:5: error: 'endl' was not declared in this scope ------------------------------------------------------------------------ ---------------------------------------- The Old "Hello World": Makefile: hello: hello.c ${CC} ${CFLAGS} ${LDFLAGS} -o hello hello.c The Old "Hello World" saved as Hello.c #include "stdio.h" main(){ printf ("Hello Out There"); } The Result: root@overo:~/temp# make hello.c makefile:3: *** missing separator. Stop. ------------------------------------------------------------------------ -------------------------------------------- Any ideas ?? Thanks ... "People sleep peaceably in their beds at night only because rough men stand ready to do violence on their behalf." - George Orwell |
From: William P. S. I. <bil...@xp...> - 2011-02-17 23:05:56
|
Could it be that there is a "path" environment variable that has to be set, which points to where ever stdio.h is located ? BTW this is the version I HAVE to get working L From: Pettinato, Jim [mailto:Jim...@fm...] Sent: Thursday, February 17, 2011 5:18 PM To: General mailing list for gumstix users. Subject: Re: [Gumstix-users] Hello World Tutorial Problems :( Somehow your source file lost the "stdio.h" file reference in the #include statement. From: William Pretty Security Inc [mailto:bil...@xp...] Sent: Thursday, February 17, 2011 5:10 PM To: 'General mailing list for gumstix users.' Subject: [Gumstix-users] Hello World Tutorial Problems :( Well I installed the native SDK and then tried both "Hello World" examples . I'm not much of a C++ programmer but here's what I got: The new "Hello World": Saved as 'hellothere.cpp' #include using namespace std; int main() { cout << "Gumstix can natively compile C++" << endl; return 0; } The Result: root@overo:~/temp# g++ -o hello hellothere.cpp hellothere.cpp:1:10: error: #include expects "FILENAME" or <FILENAME> hellothere.cpp: In function 'int main()': hellothere.cpp:5: error: 'cout' was not declared in this scope hellothere.cpp:5: error: 'endl' was not declared in this scope ---------------------------------------------------------------------------- ------------------------------------ The Old "Hello World": Makefile: hello: hello.c ${CC} ${CFLAGS} ${LDFLAGS} -o hello hello.c The Old "Hello World" saved as Hello.c #include "stdio.h" main(){ printf ("Hello Out There"); } The Result: root@overo:~/temp# make hello.c makefile:3: *** missing separator. Stop. ---------------------------------------------------------------------------- ---------------------------------------- Any ideas ?? Thanks . "People sleep peaceably in their beds at night only because rough men stand ready to do violence on their behalf." - George Orwell No virus found in this incoming message. Checked by AVG - www.avg.com Version: 9.0.872 / Virus Database: 271.1.1/3435 - Release Date: 02/17/11 02:34:00 |
From: Markus S. <msv...@ae...> - 2011-02-17 23:15:59
|
William, Try this: #include <iostream> int main() { std::cout << "Gumstix can natively compile C++\n"; return 0; } You were missing the <iostream> up near the top. Also, I removed the "using namespace std" because it is BAD BAD practice to suck the entire std namespace into the global namespace. It is cleaner to use "using std::cout" instead, to import only what you will need. It is true that practically every C++ "hello world" tutorial uses "using namespace std" but it's still bad. Regards, Markus. On 17/02/2011 6:05 PM, William Pretty Security Inc wrote: > > #include > > using namespace std; > > int main() { > > cout << "Gumstix can natively compile C++" << endl; > > return 0; > > } > |
From: William J. <wg...@ca...> - 2011-02-17 23:20:43
|
try changing: #include to be: #include <iostream> On 2/17/2011 4:09 PM, William Pretty Security Inc wrote: > > Well I installed the native SDK and then tried both "Hello World" > examples ... > > I'm not much of a C++ programmer but here's what I got: > > The new "Hello World": Saved as 'hellothere.cpp' > > #include > > using namespace std; > > int main() { > > cout << "Gumstix can natively compile C++" << endl; > > return 0; > > } > > The Result: > > root@overo:~/temp# g++ -o hello hellothere.cpp > > hellothere.cpp:1:10: error: #include expects "FILENAME" or <FILENAME> > > hellothere.cpp: In function 'int main()': > > hellothere.cpp:5: error: 'cout' was not declared in this scope > > hellothere.cpp:5: error: 'endl' was not declared in this scope > > ---------------------------------------------------------------------------------------------------------------- > > The Old "Hello World": > > Makefile: > > hello: hello.c > > ${CC} ${CFLAGS} ${LDFLAGS} -o hello hello.c > > The Old "Hello World" saved as Hello.c > > #include "stdio.h" > > main(){ > > printf ("Hello Out There"); > > } > > The Result: > > root@overo:~/temp# make hello.c > > makefile:3: *** missing separator. Stop. > > -------------------------------------------------------------------------------------------------------------------- > > Any ideas ?? > > Thanks ... > > "People sleep peaceably in their beds at night only because rough men > > stand ready to do violence on their behalf." - George Orwell > > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > > > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: alxx <al...@al...> - 2011-02-18 05:57:15
|
> Well I installed the native SDK and then tried both "Hello World" examples > . > > > > I'm not much of a C++ programmer but here's what I got: BIll if you would like I can post links to copies of both c and c++ tutorials written for students for the gumstix overo ? They assume some prior c and c++ knowledge. Still working on the python and fortran versions. I'll leave them up for just a few days - these are drafts c++ version I still need to fix up the section on namespaces word documents http://dl.dropbox.com/u/3211570/tutorial1.zip Alex |
From: alxx <al...@al...> - 2011-02-18 06:03:20
|
oops got the link wrong http://dl.dropbox.com/u/3211570/Tutorial_part1.zip Alex >> Well I installed the native SDK and then tried both "Hello World" >> examples >> . >> >> >> >> I'm not much of a C++ programmer but here's what I got: > > > BIll if you would like I can post links to copies of both c and c++ > tutorials written for students for the gumstix overo ? > > > They assume some prior c and c++ knowledge. > Still working on the python and fortran versions. > > I'll leave them up for just a few days - these are drafts > > c++ version I still need to fix up the section on namespaces > > word documents > http://dl.dropbox.com/u/3211570/tutorial1.zip > > > Alex > > > > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Cole C. <col...@gm...> - 2011-02-18 07:09:39
|
This is a helpful link about include and library problems http://www.network-theory.co.uk/docs/gccintro/gccintro_21.html <http://www.network-theory.co.uk/docs/gccintro/gccintro_21.html>essentially, you should check /usr/include and /usr/local/include for iostream.h Also, when you are trying to fix compile errors, only try to fix the topmost error. A mistake in one place can cause a few to a few hundred errors in other places with perfectly good code. for the Makefile all you need to successfully compile these two programs is the following the details of how to compile and everything happen automatically! I'm not up to writing a tutorial to make just now, though simple beginners tutorials that aren't wildly confusing are hard to come by #begin Makefile all: hello hellothere hello: hellothere: #end Makefile On Fri, Feb 18, 2011 at 12:03 AM, alxx <al...@al...> wrote: > > oops got the link wrong > > http://dl.dropbox.com/u/3211570/Tutorial_part1.zip > > Alex > > > >> Well I installed the native SDK and then tried both "Hello World" > >> examples > >> . > >> > >> > >> > >> I'm not much of a C++ programmer but here's what I got: > > > > > > BIll if you would like I can post links to copies of both c and c++ > > tutorials written for students for the gumstix overo ? > > > > > > They assume some prior c and c++ knowledge. > > Still working on the python and fortran versions. > > > > I'll leave them up for just a few days - these are drafts > > > > c++ version I still need to fix up the section on namespaces > > > > word documents > > http://dl.dropbox.com/u/3211570/tutorial1.zip > > > > > > Alex > > > > > > > > > > > ------------------------------------------------------------------------------ > > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > > Pinpoint memory and threading errors before they happen. > > Find and fix more than 250 security defects in the development cycle. > > Locate bottlenecks in serial and parallel code that limit performance. > > http://p.sf.net/sfu/intel-dev2devfeb > > _______________________________________________ > > gumstix-users mailing list > > gum...@li... > > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > > > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: alxx <al...@al...> - 2011-02-18 08:56:32
|
If it talks about iostream.h its old and out of date on c++. #include <iostream> or to use c headers and libraries in c++ , you prefix them with a c. #include <cstdio> or #include <cstdlib> In my post you replied to was the link to a zip file of two tutorials for c and c++ on gumstix overo. Writen for students to use on our remote "omap" lab (uses gumstix earth). They can login from any where in the world using a web browser and remote desktop/rdesk and access the boards. http://remotelabs.eng.uts.edu.au The remotelabs pages maybe down for a week as the systems getting upgraded to the latest version. http://www.labshare.edu.au/ Available and under development labs http://www.labshare.edu.au/index.php?option=com_content&view=article&id=123&Itemid=88 Alex > This is a helpful link about include and library problems > > http://www.network-theory.co.uk/docs/gccintro/gccintro_21.html > > <http://www.network-theory.co.uk/docs/gccintro/gccintro_21.html>essentially, > you should check /usr/include and /usr/local/include for iostream.h > > Also, when you are trying to fix compile errors, only try to fix the > topmost > error. A mistake in one place can cause a few to a few hundred errors in > other places with perfectly good code. > > for the Makefile all you need to successfully compile these two programs > is > the following > > the details of how to compile and everything happen automatically! I'm not > up to writing a tutorial to make just now, though simple beginners > tutorials > that aren't wildly confusing are hard to come by > > #begin Makefile > all: hello hellothere > > hello: > > hellothere: > > #end Makefile > > On Fri, Feb 18, 2011 at 12:03 AM, alxx <al...@al...> wrote: > >> >> oops got the link wrong >> >> http://dl.dropbox.com/u/3211570/Tutorial_part1.zip >> >> Alex >> >> > BIll if you would like I can post links to copies of both c and c++ >> > tutorials written for students for the gumstix overo ? >> > >> > >> > They assume some prior c and c++ knowledge. >> > Still working on the python and fortran versions. >> > >> > I'll leave them up for just a few days - these are drafts >> > >> > c++ version I still need to fix up the section on namespaces >> > >> > word documents >> > http://dl.dropbox.com/u/3211570/tutorial1.zip >> > >> > >> > Alex |