----- 原文 -----

From: Sorin Mustaca

To: [EMAIL PROTECTED]

Cc: [email protected]

Subject: Re: [mico-devel] I think there are some mistakes in the mico-2.3.12.

Sent: Wed Aug 09 16:14:38 CST 2006

When I used the makefile.win32 , i met a mistake .

The description of the mistake is

"building threadVC2.lib and object pthreadvc2.exp"

"LINK : fatal error LNK2023: wrong dll or enterpoint 'msobj71.dll'

"NMAKE : fatal error u1077 : "cl" : return code "0x2"

"stop"

I download the package from Redhat ,then use the pthread.dsp and pthread.dsw to build the dll.

After that ,use makefile.win32 . Success!

> Hi,

> Please observe the build process of Pthreads inside MICO.

> We compile with makefile and not with DSP/VCPROJ.

>

> That DSP file is left there because it is/was contained in the original

> package from Redhat.

>

> Sorin

>

> [EMAIL PROTECTED] wrote:

> > please checking the files unde! r the folder mico-2.3.12micocontribpthreads.

> >

> > I met a problem when i was trying to compile the mico 2.3.12 ,using

> > vc++7.1.

> >

> > I found the problem caused by the pthreads.(pthreadVC2.dll can't be

> > output )

> >

> > The pthread.dsp doesn't work ,and maybe there are some mistakes in the

> > makefile.

> >

> > I downloaded a new source from the web

> > site:http://sources.redhat.com/pthreads-win32/ ,

> >

> > then it can work well.

> >

> > ------------------------------------------------------------------------

> > 超大U盘免费等你拿

> >

> > *用搜狗拼音写邮件,体验更流畅的中文输入>>

> >

> >

> >

> > ------------------------------------------------------------------------

> >

> > _______________________________________________

> > Mico-devel mailing list

> > [email protected]

> > http://www.mico.o! rg/mailman/listinfo/mico-devel

>

> --

> Regards,

>

> Sori n Mustaca

> Website: http://www.mustaca.de

> Blog:http://www.mustaca.de/blog

>



超大U盘免费等你拿
*用搜狗拼音写邮件,体验更流畅的中文输入>>
_______________________________________________
Mico-devel mailing list
[email protected]
http://www.mico.org/mailman/listinfo/mico-devel

Reply via email to