L'octidi 28 messidor, an CCXXIV, Jonathan Dowland a écrit :
> Interesting nuance, thanks!
>
> I wonder if this is why SDL recommends people just use "" for their
> own headers.
The best explanation I can come up with is that their examples where
originally designed as test programs within the sou
On Fri, Jul 15, 2016 at 02:59:12PM +0200, Andre Majorel wrote:
> The rule of thumb of using "" for application headers and <> for
> system headers is valid. But a more accurate way to summarise
> the difference would be that #include <> only looks at the
> system directories.
Interesting nuance, t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Jul 15, 2016 at 02:59:12PM +0200, Andre Majorel wrote:
> On 2016-07-15 11:54 +0200, to...@tuxteam.de wrote:
>
> > As your includes are written above, the C compiler would look
> > for a file md5.h in the current compilation directory: most
> >
On 2016-07-15 11:54 +0200, to...@tuxteam.de wrote:
> As your includes are written above, the C compiler would look
> for a file md5.h in the current compilation directory: most
> probably there isn't one, since whatever package you installed
> will put it in a standard system location, typically u
Hi,
Pol Hallen wrote:
> now I've many errors
> alice.c:50:18: error: unknown type name ‘md5_context’
> alice.c:61:37: error: unknown type name ‘uint8’
This might indicate that openssl/md5.h is not the md5.h which is needed
for your source code. If so, then was rather a red herring.
(One can be r
On Fri, Jul 15, 2016 at 12:23:01PM +0200, Jens Sauer wrote:
> I think you are missing dependencies from the ssl library. Have a look into
> the docs [1].
Doesn't look like openssl to me. Openssl just happens to also have a md5.h
header in it.
signature.asc
Description: Digital signature
I think you are missing dependencies from the ssl library. Have a look into
the docs [1].
Your questions implies that you are not very experienced in C coding.
Maybe you should ask yourself the question if starting with a complex and
potential security risky api like openssl is the right thing for
On Fri, Jul 15, 2016 at 12:07:09PM +0200, Pol Hallen wrote:
> alice.c:50:18: error: unknown type name ‘md5_context’
> void md5_starts( md5_context *ctx )
These aren't typedefs used by openssl. It looks like your code
is designed to be used with a completely different md5.h.
FWIW, last time I wa
Hi,
i second tomás' assessment and proposal.
Reco wrote:
> #include with encased in 'less' and 'more' characters instructs
> preprocessor to search header files system-wide. A search path can be
> modified with -L flag.
It is not a system-wide search, but rather a search iterating over a list
o
L'octidi 28 messidor, an CCXXIV, Pol Hallen a écrit :
> #include
> #include
> #include
> #include "md5.h"
The fact that md5.h is included with double quotes instead of angle brackets
means that it is a header local to the project, not a system header. Your .c
file should come with the md5.h fil
sorry, my mistake about the package (I use debian testing)
find /usr/include -name md5.h
find /usr/include/ -name md5.h
/usr/include/openssl/md5.h
/usr/include/crypto++/md5.h
#include
now I've many errors
thanks for help!
alice.c:50:18: error: unknown type name ‘md5_context’
void m
#include
I've same problem :-/
--
Pol
Hi.
On Fri, Jul 15, 2016 at 11:34:38AM +0200, Pol Hallen wrote:
> Hi, all
>
> I've this error:
>
> fatal error: md5.h: No such file or directory
> compilation terminated.
>
> when I compiled a source C
>
> gcc source.c
>
> [...]
> #include
> #include
> #include
> #include "md5.h"
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Jul 15, 2016 at 11:34:38AM +0200, Pol Hallen wrote:
> Hi, all
>
> I've this error:
>
> fatal error: md5.h: No such file or directory
> compilation terminated.
>
> when I compiled a source C
>
> gcc source.c
>
> [...]
> #include
> #include
14 matches
Mail list logo
