Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I am getting Parse errors in a header file, which is written in C language. I am running it on LINUX OS. I checked the lines in which it is giving parse errors but I didn't find anyhting wrong. Can anybody tell me how to solve these errors?? is there any tools find out the parse errors or hidden characters ??? The output is
/usr/local/include/vipl.h:74: parse error before "VIP_UNIT64"
/usr/local/include/vipl.h:75: parse error before "VIP_UNIT32"
/usr/local/include/vipl.h:76: parse error before "VIP_UNIT16"
/usr/local/include/vipl.h:77: parse error before "VIP_UNIT8"
/usr/local/include/vipl.h:100: parse error before "VIP_MEM_HANDLE"
/usr/local/include/vipl.h:112: parse error before "VIP_UINT16"
/usr/local/include/vipl.h:114: parse error before "HostAddress"
/usr/local/include/vipl.h:115: parse error before '}' token
/usr/local/include/vipl.h:145: parse error before "VIP_UINT16"
/usr/local/include/vipl.h:146: parse error before '*' token
/usr/local/include/vipl.h:148: parse error before "MaxDiscriminatorLen"
/usr/local/include/vipl.h:162: parse error before '}' token
/usr/local/include/vipl.h:175: parse error before "VIP_UINT64"
/usr/local/include/vipl.h:177: parse error before '}' token
/usr/local/include/vipl.h:184: parse error before "VIP_PVOID64"
/usr/local/include/vipl.h:186: parse error before "SegCount"
/usr/local/include/vipl.h:187: parse error before "Control"
/usr/local/include/vipl.h:188: parse error before "Reserved"
/usr/local/include/vipl.h:189: parse error before "ImmediateData"
/usr/local/include/vipl.h:190: parse error before "Length"
/usr/local/include/vipl.h:191: parse error before "Status"
/usr/local/include/vipl.h:199: parse error before "VIP_PVOID64"
/usr/local/include/vipl.h:201: parse error before "Reserved"
/usr/local/include/vipl.h:209: parse error before "VIP_PVOID64"
/usr/local/include/vipl.h:211: parse error before "Length"
/usr/local/include/vipl.h:217: parse error before "VIP_ADDRESS_SEGMENT"
/usr/local/include/vipl.h:227: parse error before "VIP_CONTROL_SEGMENT"
/usr/local/include/vipl.h:229: parse error before '}' token
/usr/local/include/vipl.h:347: parse error before "VIP_DESCRIPTOR"
/usr/local/include/vipl.h:351: parse error before '}' token
/usr/local/include/vipl.h:387: parse error before "VIP_NET_ADDRESS"
/usr/local/include/vipl.h:389: parse error before '}' token
/usr/local/include/vipl.h:396: parse error before string constant
you can possibly solve your problem opening the file with another editor. Vi, Vim, gvim, emacs or xemacs are trusted by a lot of people and they usually don't hide control characters. Try to open it with one of these, and see what happens.