I'm not sure about compiling in.h.
The syntax <="" a=""><b>IPPROTO_IP</b> is challenging.
I have several versions of the library, most have includes that turn into rabbit holes.
I just need the xdr rpc library to link with a SW project. It's just easier to include it rather than remove it...
Thank you, tried that.
Just to be clear, I'm using Windows7, GCC-5.2, and a MinGW msys-1.0 command window.
I call success being able to download the source, execute ./configure, make, and make install, with no errors.
I have attempted this with:
fxdr_2.1c,
glibc-2.23,
portablexdr-4.91...
Maybe that's my problem, I'm mixing windows and Linux.
I'm using Windows7, GCC 5.2, MinGW command-line and make.
Searching for information, I read somewhere that MinGW no longer includes some essential variable types, so this project has changed from a compile link and run to a minor rewrite...
Making progress.
Next error involves macros,
and reviewing Kernigen and Ritchie
4.11.2 Macro Substitution
A definition has the form
#define name replacement text
It calls for a macro substitution of the simplest kind-subsequent occurrences of
the token name will be replaced by the replacement...
Sometimes open source projects compile link and run effortlessly which motivates you to try another, like this project, which requires the xdr components from glibc.
The source code is readily available but the headers account for half the code.
It's convoluted because of all the ifdef...
Non-C programmer here.
I'm using GCC and Gfortran V5.2 (which BTW self compiled perfectly), on Windows7(64).
I'm getting this C error.
rpc/types.h:78:9: error: unknown type name '__u_char'
typedef __u_char u_char;
What does the double underscore do, what does it mean?
Thank you.
Non C programer here.
The headers at the top of a C function are my problem.
From the "compiler/operating-system/effective" point of view, what's the difference between
#include <rpc/xdr.h>
#include "rpc/xdr.h"
Both yield errors.
The compiler can't find the directory in <> version.
The...