Re: UUIDs generated using ossp-uuid on windows not unique

<br /> <br /> > To: anaeem.it@hotmail.com<br />> CC: dpage@postgresql.org; z-saito@guitar.ocn.ne.jp;
pgsql-hackers@postgresql.org<br/>> Subject: Re: [HACKERS] UUIDs generated using ossp-uuid on windows not unique <br
/>>Date: Tue, 30 Mar 2010 10:01:50 -0400<br />> From: tgl@sss.pgh.pa.us<br />> <br />> MUHAMMAD ASIF
<anaeem.it@hotmail.com>writes:<br />> > I have downloaded uuid-1.6.2.tar.gz from
http://www.ossp.org/pkg/lib/uuid/. It successfully built with MinGW gcc and made libuuid.a, I renamed it to uuid.lib to
builduuid-ossp contrib module with visual studio 2005. uuid-ossp give the following linker error with VC2005 i.e.<br
/>>>    <br />> >     Linking...<br />> >     Creating library Release\uuid-ossp\uuid-ossp.lib and
objectRelease\uuid-ossp\uuid-ossp.exp<br />> >     uuid.lib(uuid_time.o) : error LNK2019: unresolved external
symbol___divdi3 referenced in function _uuid_time_gettimeofday<br />> >     uuid.lib(uuid_time.o) : error
LNK2019:unresolved external symbol ___moddi3 referenced in function _uuid_time_gettimeofday<br />> >    
uuid.lib(uuid_str.o): error LNK2019: unresolved external symbol ___umoddi3 referenced in function _fmtint<br />>
>    uuid.lib(uuid_str.o) : error LNK2019: unresolved external symbol ___udivdi3 referenced in function _fmtint<br
/>>>     .\Release\uuid-ossp\uuid-ossp.dll : fatal error LNK1120: 4 unresolved externals<br />> <br />>
Generally,gcc is supposed to arrange for -lgcc to be included<br />> automatically in links if it's needed. I have
seenfailures like this<br />> before on other platforms, and it generally had something to do with<br />> using
gccfollowed by a non-gnu linker; which indeed seems to describe<br />> what you did here. I would suggest adding
-lgccto your VC project;<br />> or maybe where it actually went missing was in your build of libuuid.<br />> <br
/><br/><p style="MARGIN: 0in; FONT-FAMILY: Calibri; FONT-SIZE: 11pt">you are right its not good idea to generate binary
withnon compatible tools that may lead to unexpected results and could make debugging worse.<br />> > MinGW
libgcc.acontains these symbols and these routines are not<br />> > implemented in c ( its assembly code to make
itfast ) so I extracted<br />> > _divdi3.o _moddi3.o _umoddi3.o _udivdi3.o (we can add these additional<br />>
>files to uuid.lib to make build easy) from libgcc.a and link it with<br />> > uuid-ossp contrib.<br />>
<br/>> This seems entirely inappropriate; it makes unwarranted assumptions<br />> about which parts of libgcc are
needed,and we couldn't ship any such<br />> thing anyhow for license reasons.<br />> <br />> regards, tom
lane<br/><br /><p style="MARGIN: 0in; FONT-FAMILY: Calibri; FONT-SIZE: 11pt">I dont know much about licencing , I was
assumingthat if we can create application with gcc then we can use parts of gcc according to our will too.  that was a
wrongassumption, thank you for details :).<p style="MARGIN: 0in; FONT-FAMILY: Calibri; FONT-SIZE: 11pt"><br />Best
Regards,<pstyle="MARGIN: 0in; FONT-FAMILY: Calibri; FONT-SIZE: 11pt">Asif Naeem<p style="MARGIN: 0in; FONT-FAMILY:
Calibri;FONT-SIZE: 11pt"> <br /><hr />Hotmail: Trusted email with Microsoft’s powerful SPAM protection. <a
href="https://signup.live.com/signup.aspx?id=60969"target="_new">Sign up now.</a>