Hi,
There is no config.log on disk. What I see in the log I send (which is just
the console output) normally we see:
checking how to run the C preprocessor... i686-pc-cygwin-gcc -E
But with multilib (I think), I see:
checking how to run the C preprocessor... /lib/cpp
Johnny
Checking multilib
Use dlltool, exact parameters depend on the info you have (def file I hope)
--
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distributi
I think the file got truncated. Can you send the complete file to me in
private E-mail ? (The private copy you sent was also truncated.)
The file I got is "only" 5524 lines long, doesn't contain the word
sanity.
Danny
On Thu, 2009-06-11 at 14:12 +0200, Johnny Willemsen wrote:
> Hi,
>
>
On Thu, 11 Jun 2009 17:47:32 +0200, Danny Backx
wrote:
> Can you spell out the different steps you perform ?
>
> And I would expect you to obtain two things :
> - a real DLL (libgynoid.dll), to be copied to the device
> - an import library (libgynoid.dll.a), to be used in development
> to get t
On Thu, 2009-06-11 at 00:02 +0200, Vincent R. wrote:
> OK finally I found enough information from MSDN to rebuild the definitions
> with the exceptions
> of CEVT_ (I put in comment msdn url from which I got the information).
> So please find the two includes and if I can find missing definition
Can you spell out the different steps you perform ?
And I would expect you to obtain two things :
- a real DLL (libgynoid.dll), to be copied to the device
- an import library (libgynoid.dll.a), to be used in development
to get the application to link.
I only saw one mentioned in your message. M
On Thu, 2009-06-11 at 10:10 +0200, Sébastien Lorquet wrote:
> for my information, is the following an acceptable way to find unknown
> constant values?
>
>
> #include proper header
>
>
> int main() {
> printf("PIMPR_FIRST_NAME = %d",PIMPR_FIRST_NAME );
> }
This is really just another way t
(assume Pawel's drunk, plz)
You were looking for a way to determine the values of some
constants that I assume are hard to derive. Your code piece
used compiled code to print out the value of an unknown
constant. Without going deep into the nature of the problem,
I've proposed using preprocessor f
On Thu, 11 Jun 2009 17:15:40 +0900, Pawel Veselov
wrote:
> I would do that:
>
> [...@e03077]/tmp$ cat > /tmp/1.c
> #include
> _CTYPE_Q
> [...@e03077]/tmp$ gcc -E /tmp/1.c |tail
> {snip}
> 0x0020L
> [...@e03077]/tmp$
>
Am I missing something ? what is 1.c ?
why are you including ctype.h ?
A
I would do that:
[...@e03077]/tmp$ cat > /tmp/1.c
#include
_CTYPE_Q
[...@e03077]/tmp$ gcc -E /tmp/1.c |tail
{snip}
0x0020L
[...@e03077]/tmp$
On Thu, Jun 11, 2009 at 5:10 PM, Sébastien Lorquet wrote:
> for my information, is the following an acceptable way to find unknown
> constant values?
>
for my information, is the following an acceptable way to find unknown
constant values?
#include proper header
int main() {
printf("PIMPR_FIRST_NAME = %d",PIMPR_FIRST_NAME );
}
Regards
Sebastien
(PS: sorry vincent for my email, it was for the list but gmail failed the
"reply to the list" )
-
11 matches
Mail list logo
