Hi Brian,
Do you have Cygwin installed on your machine for other purposes? There
can be only one copy of cygwin1.dll on your machine. If there are mosre
the DLL just complains it can see other versions. For this reason the
installer checks to see if cygwin1.dll is already installed on your
machine, and will not install a new copy if it is there. However (isn't
there always a however :-) ), if the copy of cygwin1.dll you have is new
very new, it will be incompatible with the msgpcc code. That older copy
of cygwin1.dll may have been put there put an older install of mspgcc,
or by something else that uses Cygwin (maybe a full install of the
Cygwin package). If mspgcc installs a copy of cygwin1.dll it puts it in
c:/mspgcc. It something else installed a copy, then I have no idea where
it might be. However, if that old copy is removed, and a new copy
installed (you reinstall mspgcc, update you install of Cygwin, or
whatever) you should be OK.
I should make this an FAQ!
Regards,
Steve
BRIAN OTT wrote:
So what is the installation procedure for this? I tried to uninstall
the old and deleted all the files, then installed the new, but I still
get the error message.
Regards,
Brian ott
> Hi,
>
> I have been running the MSPGCC tools on my WIN2K machine since April.
> This installation was based on mspgcc-030306.exe. I decided today it
was
> time to upgrade to get patches and fixes. I downloaded
> mspgcc-20030506.exe and installed, now when I try to build my code I
get
> a pop-up with the message
>
> "msp430-gcc.exe - Entry Point Not Found !X! The procedure entry point
> mempcpy could not be located in the dynamic link library cygwin1.dll".
>
> Note, this is note an error output of the compiler but rather and
> Windows popup on execution of GCC. Any thoughts? Have I done something
> wrong? If I go back to the previous version everything seems to work
> once again.
you have to remove the cygwin1.dll of the old installation and redo the
new installation.
(the new installed does not copy the cygwin1.dll if there is already
one, but unfortunately the old dll is not compatible with the new one...)
chris
