Tag Info

New answers tagged

1

Compatibility I guest, in my case I was having This problem in a laptop with Debian Jessie, the right thing was : aptitude install qt4-qtconfig user@host$ moc moc: could not exec '/usr/lib/x86_64-linux-gnu/qt4/bin/moc': No such file or directory According to /usr/share/doc/moc/README.Debian we need to run: user@host$mocp in addition to that ...


0

In short: It's available via apt-get with: sudo apt-get install libois-dev and/or sudo apt-get install libois-1.3.0 In long: Based on all the warnings in the boot strap and configure I think it's just a wee bit old. The repo has not been touched in 5 years or so although there are some forks. As for install ogre via apt this is also possible, but ...


0

To answer the problem about eclipse and the c++ module. It's a bug with RHEL that exists in centos and scientific too. You need to run eclipse as root once after installing the C++ modules via yum. I honestly don't remember why, but it will work as a regular user after that. To install new software you can use yum. To look for the appropriate package you ...


0

grep -v '[^0-9]' <infile |./cprogram That would only print empty lines or lines containing only numbers at your program. You could also edit each line... sed 's/[^0-9]//g' <infile |./cprogram You can filter empties... sed -n 's/[^0-9]//g;/./p' <infile |./cprogram Or you might want to include . and/or sign: sed -n 's/[^- .0-9]//g ...


1

You seem to have come pretty close to something that should work.  I would modify it to: while IFS= read -r l; do printf "%s\n" "$l" | ./c_program; done < test_numbers.txt Say read l rather than read $l. Use read -r to read "raw" lines (don't interpret backslashes). Use IFS= to capture leading and trailing spaces. Don't say printf "$l"; that will ...


0

awk {'print $1'} test_numbers.txt |./c_program


3

You need to use clang++. clang is the C compiler, clang++ is the C++ compiler. Like gcc. I think these are basically the same compiler under the hood, but (again like gcc), clang++ links against the C++ libraries by default, while clang doesn't. Hence the linker errors.


1

You don't have to do anything as these are warnings not errors. What you could do is notify the maintainers of the package and let them know that warnings are confusing to the non-initiated and if they can get rid of them. If you do make sure to provide them with your setup information, as they might not see the warning in theirs.



Top 50 recent answers are included