1. #include <stdint.h>
2. sys/types.h - as name suggests is system specific (normally this might come with the kernel as it is on Linux, glibc uses particular version of kernel headers which provide...
Type: Posts; User: bboozzoo
1. #include <stdint.h>
2. sys/types.h - as name suggests is system specific (normally this might come with the kernel as it is on Linux, glibc uses particular version of kernel headers which provide...
who cares, OP doesn't have a clue anyway
uhuh google? c-ares seems to be fine wrt. licensing
#define MAX_PASS_LEN 10
struct device_pass_s {
char pass[MAX_PASS_LEN];
};
/* then the ioctl call should be the following */
struct device_pass_s pass = {
.pass = "mypass"
};
uhhh, given that you mention 'giving space for ip_h, ...' you don't seem to be opening SOCK_STREAM, but rather SOCK_RAW or even PF_PACKET. can you explain why?
you need to have a toolchain for architecture, one can be built using buildroot: http://buildroot.uclibc.org/ or scratchbox: http://scratchbox.org/
how is the code of myfile supposed to know the how mystruct looks like?
omg, what's so bad about inet_aton/inet_pton that prevents you from using it? just take the IP address part from the string, pass is through inet_*ton, then & with the mask and you're done. Of course...
uhh write down this code and get it actually compiled, if x, y, z are not stored in registers then change your compiler (btw. the loop is pointless, so the compiler would most probably just get rid...
my dear, why not just use shell script instead?
Well it's not so hard actually, as long as you know what you're doing and don't care about screwing up libc allocator (never tested it though, but I do not see any reason why it should not).
On UNIX...
https://www.cs.colostate.edu/wiki/Gdb here's a decent bunch of references to number of tutorials
being extra lazy you can always use std::for_each from <algorithm> or if you need to break the loop explicitly at some point (and writing C++ code, you're likely to have Boost laying around)...
not really array[1][4] is an array of char[4] with only 1 element
why not use something like this:
#define MAX_FIELD_LEN 40
struct tuple_s {
char field1[MAX_FIELD_LEN];
char...