Lcc and Windows 7
Marco Basaldella
that I previous successflully compiled and ran with gcc(minGW). My aim
was to switch to lcc-win32 and later to lcc-win64, since my code is
very memory hungry.
Well, I simple downloaded lcc-win32, lcc-win64, installed them, put c:
\lcc\bin in my windows' PATH, and tried to have my program working
with lcc. When I compile the code, everything goes fine; the compiler
outputs a executable, but when I try to run it, this .exe fails to
start. Windows gives my a strange error - 16 bit application not
supported. Why the hell should this a 16 bit application, if I
compiled it with lcc-win32 (and lcc-win64 gives the same error!)
Not satisfied by this experience, I tried to open the lcc-win64
editor, but wedit64 fails to start with error 0xc0150002. Switching to
wedit32, everywhing works fine. Then, I followed the tutorial step-by-
step, and imported my code in a new lcc project; then, I tried to
compile it, having as result a bunch of library missing error (i.e.,
_malloc, _fclose, _fopen, in a missing crtdll.lib). I try to use the
automatic library adder but it didn't work.
I thought it was my fault and I was missing something in lcc, so I
went on http://www.q-software-solutions.de/products/lcc-win32/tutorial.shtml
and I made the tutorial again step-by-step, compiling a simple hello
world, as shown in that page. The result was the same, _crtdll.lib
missing, and "add library" button didn't work.
Am I missing something, I'm simply stupid or is there something wrong
with lcc and Windows 7? Why does lcc-64 graphical editor refuse to
start? What are all those libraries missing?
Thanks in advance to everyone for helping me,
Marco
jacob navia
There are problems with lcc-win64, and I have a missing dll problem
That is why wedit64 refuses to start. In the good old times windows
would stop with
missing dll "dll name"
But that was too user friendly (you would know which dll was missing
and you could fix it)
Now windows throw a meaningless message and doesn't tell the name of
the dll so that you can't fix it!
Marco Basaldella
at least MSVCR80D.dll and IESHIMS.DLL are missing. Do you know where I
can get them and where do I have to install them?
Do you have a solution for the 16 bit error message and the
_crtdll.lib missing errors? I have to add some include in my code? If
I simply want to use the command line utility, is there any option
that I have to use or some library to link to have my code properly
working?
Thank you for your support and for your great work with LCC,
Marco
On Feb 5, 11:24 pm, jacob navia <ja...@nospam.org> wrote:
> Marco Basaldella a écrit :
>
>
>
>
>
> > I premise I'm running Windows 7 x64 and I'm trying to compile code
> > that I previous successflully compiled and ran with gcc(minGW). My aim
> > was to switch to lcc-win32 and later to lcc-win64, since my code is
> > very memory hungry.
>
> > Well, I simple downloaded lcc-win32, lcc-win64, installed them, put c:
> > \lcc\bin in my windows' PATH, and tried to have my program working
> > with lcc. When I compile the code, everything goes fine; the compiler
> > outputs a executable, but when I try to run it, this .exe fails to
> > start. Windows gives my a strange error - 16 bit application not
> > supported. Why the hell should this a 16 bit application, if I
> > compiled it with lcc-win32 (and lcc-win64 gives the same error!)
>
> > Not satisfied by this experience, I tried to open the lcc-win64
> > editor, but wedit64 fails to start with error 0xc0150002. Switching to
> > wedit32, everywhing works fine. Then, I followed the tutorial step-by-
> > step, and imported my code in a new lcc project; then, I tried to
> > compile it, having as result a bunch of library missing error (i.e.,
> > _malloc, _fclose, _fopen, in a missing crtdll.lib). I try to use the
> > automatic library adder but it didn't work.
>
> > I thought it was my fault and I was missing something in lcc, so I
> > went onhttp://www.q-software-solutions.de/products/lcc-win32/tutorial.shtml
jacob navia
Does gmail accepts binary attachements?
Thanks
ArarghMai...@not.at.arargh.com
wrote:
>Can I mail you those dlls?
>Does gmail accepts binary attachements?
If you rename the files to .JPG, yes. I just had to go thru that
mess.
>
>Thanks
--
ArarghMail002 at [drop the 'http://www.' from ->] http://www.arargh.com
BCET Basic Compiler Page: http://www.arargh.com/basic/index.html
To reply by email, remove the extra stuff from the reply address.
Keith Thompson
> On Sat, 06 Feb 2010 21:28:35 +0100, jacob navia <ja...@spamsink.net>
> wrote:
>
>>Can I mail you those dlls?
>>Does gmail accepts binary attachements?
>
> If you rename the files to .JPG, yes. I just had to go thru that
> mess.
Really? I just sent a 1-kbyte random data file as an attachment to a
gmail account, and it went through with no problem.
--
Keith Thompson (The_Other_Keith) ks...@mib.org <http://www.ghoti.net/~kst>
Nokia
"We must do something. This is something. Therefore, we must do this."
-- Antony Jay and Jonathan Lynn, "Yes Minister"
Marco Basaldella
I know that gmail does not accept exe files as attachment, even if
compressed, but I really don't know about dll. You may try or simple
rename them in filename.dl , so gmail will accept them.
Thank you for your help, I can't get out of this situation by myself!
Marco
ArarghMai...@not.at.arargh.com
wrote:
>ArarghMai...@NOT.AT.Arargh.com writes:
>> On Sat, 06 Feb 2010 21:28:35 +0100, jacob navia <ja...@spamsink.net>
>> wrote:
>>
>>>Can I mail you those dlls?
>>>Does gmail accepts binary attachements?
>>
>> If you rename the files to .JPG, yes. I just had to go thru that
>> mess.
>
>Really? I just sent a 1-kbyte random data file as an attachment to a
>gmail account, and it went through with no problem.
Yes, as long as it's name does not end with exe, zip, gz, com, bat and
some others. All they check is the extension, not the content.
Keith Thompson
Ah, I see. Google explains this at
<http://mail.google.com/support/bin/answer.py?answer=6590>.
Renaming the file seems to avoid the problem. I suggest appending
something to the name rather than changing the suffix; for example,
"random.exe" is blocked, but "random.exe_" is not (and it lets the
recipient know what kind of file it really is).
Zip files are blocked only if they contain files with forbidden
suffixes, and only if they're actually named *.zip. So if you
want to send a zipped copy of foo.exe, you can either rename it to
foo.exe_ and include it in foo.zip, or include foo.exe in foo.zip
and rename foo.zip to foo.zip_ (the latter is probably easier for
the recipient to deal with).
Of course the whole point of this is to protect users from opening
harmful files, so don't open executable attachments unless you're
sure they're ok.
Marco Basaldella
files: I compress them in a folder, and then I encrypt its content,
including the file list, so gmail doesn't know what files am I really
sending. Obviously, I also include the password for the compressed
file in the text of my email, otherwise neither the receiver and not
only gmail can't read the content...
Marco
On Feb 7, 9:54 pm, Keith Thompson <ks...@mib.org> wrote:
ArarghMai...@not.at.arargh.com
<basaldel...@gmail.com> wrote:
>Thank you, but I already found a valid solution for sending executable
>files: I compress them in a folder, and then I encrypt its content,
>including the file list, so gmail doesn't know what files am I really
>sending. Obviously, I also include the password for the compressed
>file in the text of my email, otherwise neither the receiver and not
>only gmail can't read the content...
Encrypting the file isn't necessary. Currently, anyway. I know from
recent(last week) experience that gmail only checks the extension, and
not the contents. I have been renaming the files from .zip to .jpg.
The zip files contained .exe files. I am pretty sure that any file
extension not on their list will pass.
Keith Thompson
> On Sun, 7 Feb 2010 13:40:00 -0800 (PST), Marco Basaldella
> <basaldel...@gmail.com> wrote:
>>Thank you, but I already found a valid solution for sending executable
>>files: I compress them in a folder, and then I encrypt its content,
>>including the file list, so gmail doesn't know what files am I really
>>sending. Obviously, I also include the password for the compressed
>>file in the text of my email, otherwise neither the receiver and not
>>only gmail can't read the content...
>
> Encrypting the file isn't necessary. Currently, anyway. I know from
> recent(last week) experience that gmail only checks the extension, and
> not the contents. I have been renaming the files from .zip to .jpg.
> The zip files contained .exe files. I am pretty sure that any file
> extension not on their list will pass.
Not to beat a dead horse, but I suggest that renaming files from .zip
to .jpg is very likely to cause confusion, unless your recipient
*knows* that it's really a zip file. Renaming from .zip to .zip_
makes that obvious.
ArarghMai...@not.at.arargh.com
wrote:
<snip>
>Not to beat a dead horse, but I suggest that renaming files from .zip
>to .jpg is very likely to cause confusion, unless your recipient
>*knows* that it's really a zip file.
They did.
>Renaming from .zip to .zip_ makes that obvious.
Yes, but I didn't think of that. I only thought of the thing most
likely to be allowed.
Marco Basaldella
Navia, if you tell me where can I get them e where have I to put them,
I can download this dlls by myself.
Thank you very much,
Marco
jacob navia
Thanks
Marco Basaldella
> Marco Basaldella a écrit :> So what are these (in)famous dll I have to put in my computer? Mr.
The problem is still there. I can't compile, as I said in the previous
thread, because make64 it missing.
There is still the problem with lcc32. Both lcc32 and lcc64 compilers
generate executable files that my windows 7 recognize as "16-bit".
When I compile even a simple "hello world.c" using the lcc32 gui, the
error message is that this crtdll.lib is missing.
I made a screenshot, you can see it there: http://img704.imageshack.us/img704/3541/lccerror.png
.
How can I solve this problem?
Thank you for your patience,
Marco
jacob navia
The problem in the screenshot is a 32 bit problem. Apparently the system doesn't find the
c library Please go to the lcc/lib directory and tell me how big the file
LIBC.LIB
is.
Please try to compile a 64 bit hello world program with
lcc64 hello.c
lcclnk64 hello.obj
Then run it.
Does that work?
Please do it from the command line.
Thanks, and sorry for this problems
Marco Basaldella
Compiling hello.c with lcc64 and lccnk64 results in correct compiling.
the program generated runs successfully. Well done :)
Don't you worry for the problems, I think that developing such a big
program it's not as easy, expecially if you do it alone... is it?
Thanks,
Marco
On Feb 10, 5:16 pm, jacob navia <ja...@nospam.org> wrote:
> Marco Basaldella a écrit :
>
>
>
>
>
> > On Feb 9, 9:08 pm, jacob navia <ja...@nospam.org> wrote:
> >> Marco Basaldella a écrit :> So what are these (in)famous dll I have to put in my computer? Mr.
Marco Basaldella
compiler doesn't recognise the struct timeval (as defined in time.h),
but gcc and icl compiled it. How can I solve this error?
:
Thanks again for the great support,
Marco
On Feb 10, 5:16 pm, jacob navia <ja...@nospam.org> wrote:
> Marco Basaldella a écrit :
>
>
>
>
>
> > On Feb 9, 9:08 pm, jacob navia <ja...@nospam.org> wrote:
> >> Marco Basaldella a écrit :> So what are these (in)famous dll I have to put in my computer? Mr.
Keith Thompson
> Another small problem: compiling my code with lcc64 returns error: the
> compiler doesn't recognise the struct timeval (as defined in time.h),
> but gcc and icl compiled it. How can I solve this error?
struct timeval is defined by the POSIX standard, not by the
C standard. I don't know whether lcc-win supports it, but from
your description it sounds like it doesn't.
jacob navia
> Another small problem: compiling my code with lcc64 returns error: the
> compiler doesn't recognise the struct timeval (as defined in time.h),
> but gcc and icl compiled it. How can I solve this error?
> :
> Thanks again for the great support,
> Marco
>
timeval should be defined in Winsock2.h, according to
msdn pages:
http://msdn.microsoft.com/en-us/library/ms740560%28VS.85%29.aspx