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
L'octidi 28 messidor, an CCXXIV, Jonathan Dowland a écrit :
> Do not CC me, I am subscribed to the list. This is clear in the CoC
> for lists.debian.org,
Not CCing this once. I recently explained in great length why this point of
the CoC is broken and should be ignored.
>
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,
Do not CC me, I am subscribed to the list. This is clear in the CoC
for lists.debian.org, and it's prominently in the mail signature of
my mail you replied to.
On Fri, Jul 15, 2016 at 12:36:46PM +0200, Nicolas George wrote:
> L'octidi 28 messidor, an CCXXIV, Jonathan Dowland a écrit :
> > FWIW,
-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
L'octidi 28 messidor, an CCXXIV, Jonathan Dowland a écrit :
> FWIW, last time I wanted to do md5 in C, I copied the code into my own
> project. I got it from the source to dpkg, which did the same thing.
By doing that, you are depriving yourself of future bugfixes and
improvements to that
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
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
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
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
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
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
#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
>
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"
[...]
I've openssl-dev installed, but I don't understand how to audit this error..
any idea?
thanks
Hi,
I have HTML-ized documentation for a code library that contains links
to the actual header files. Clicking on the link is supposed to show
the contents of the fool.h file, for example.
However, instead of displaying the text in the netscape window,
I get a little popup showing the first few
... what I tried to do was delete all ^M chars and
all backslashes at the ends of lines. Even this wasn't enough.
are you using a make file ?
I had a problem that with the ^M in the make file made it
not work properly. What was the exact error message ?
--
TO UNSUBSCRIBE FROM THIS MAILING
I think this user has to run fromdos (in the sysutils package) on the
files, to replace the MS-DOS CR-NL line endings with just plain CR.
Thanks
Bruce
--
Bruce Perens K6BP [EMAIL PROTECTED] 510-215-3502
Finger [EMAIL PROTECTED] for PGP public key.
PGP fingerprint = 88 6A 15
MOre than once I have tried compiling C source on linux, using gcc,
that generated alot of error messages, including many concerning
backslashes at the ends of lines. An example is an existing
ghostscript driver for the HP850C Deskjet into ghostscript. The main
problem I had
In message [EMAIL PROTECTED] you wrote:
MOre than once I have tried compiling C source on linux, using gcc,
that generated alot of error messages, including many concerning
backslashes at the ends of lines.
...
Can anyone provide the slightest clue? What's special about MSDOG
source code files
Date: Fri, 18 Apr 97 20:24 GST
From: Alan Eugene Davis [EMAIL PROTECTED]
To: debian-user@lists.debian.org
MOre than once I have tried compiling C source on linux, using gcc,
that generated alot of error messages, including many concerning
backslashes at the ends of lines
24 matches
Mail list logo
