2004 DV Green Card Lottery Dates

2002-08-01 Thread info
Bu seneki DV 2004 Green Card lottery programi basvuru tarihleri ve detaylari yayinlanmistir, ayrica DV 2003 sonuclarini sitemizden bulabilirsiniz. Turkiyeden 1629 kisi bu sene ABD Green Card lotosunu kazanmistir. Bu kazananlar arasinda www.greencardusa.cc sirketi tarafindan basvuru yapan 74

Re: Automake 1.6b available.

2002-08-01 Thread Bob Ham
On Sun, 2002-07-28 at 20:17, Alexandre Duret-Lutz wrote: > If you have some time, please try it on your package and report any > issue you encounter. Especially, please shout loud if your package > works with 1.6.3 but doesn't with 1.6b. (It'll better for everybody > if we can fix compatibility

Beginner: a simple question about shared libraries

2002-08-01 Thread Ladislav Strojil
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I am sorry to ask such a simple questions but I am really lost here. I am trying to move our school project to automake. I have succeeded building programs, but I am stuck with .so files. Currently (with a hand written Makefile) it works like

Re: Automake 1.6b available and the version numbering issue

2002-08-01 Thread Respond To List Only
Alexandre; Just want to steal the soapbox here to point out that "1.6b" is more difficult for automated systems to deal with than "1.6.2". Consider the logic to determine whether 1.4-p4 is greater than 1.4.2 or 1.5. > ... works with 1.6.3 but doesn't with 1.6b. ... ...and how *is* the logic

Re: Automake 1.6b available and the version numbering issue

2002-08-01 Thread Alexandre Duret-Lutz
>>> "Respond" == Respond To List Only <[EMAIL PROTECTED]> writes: Respond> ...and how *is* the logic for 1.6b compared to 1.6.3 ? Is that like Respond> 1.(6.2).0 > 1.6.3 ? Here is how this logic is documented in the source. (Automake contains a comparison function for its version numbers, may

how to disable ylwrap?

2002-08-01 Thread John Millaway
We want to build "foo.cc" from "foo.l". Automake tries build "foo.c" instead (using ylwrap). How do we disable this entirely or at least tell automake that the output files for *.l should be named *.cc ? __ Do You Yahoo!? Yahoo! Health - Feel bet

Re: Automake 1.6b available and the version numbering issue

2002-08-01 Thread Respond To List Only
Let me preface this with the comment that, although it may lok like I'm ranting on some small issue that suddenly pushed me into a fit of rage, I'm actually sanely trying to raise points that I feel were not considered dutring the lifespan of automake and other projects. Please don't be insulted

Re: Beginner: a simple question about shared libraries

2002-08-01 Thread Alexandre Duret-Lutz
Hi! >>> "Ladislav" == Ladislav Strojil <[EMAIL PROTECTED]> writes: [...] Ladislav> I am trying to move our school project to automake. What version of Automake? [...] -- Alexandre Duret-Lutz

Re: how to disable ylwrap?

2002-08-01 Thread Alexandre Duret-Lutz
>>> "John" == John Millaway <[EMAIL PROTECTED]> writes: John> We want to build "foo.cc" from "foo.l". Automake tries John> build "foo.c" instead (using ylwrap). How do we disable John> this entirely or at least tell automake that the output John> files for *.l should be named *.cc ? I don't

Re: how to disable ylwrap?

2002-08-01 Thread John Millaway
> I don't think you can. However if you name your lexer `foo.ll' > then Automake will build `foo.cc'. I can't believe there is no way to override this. ylwrap is a most frustrating addition to automake. __ Do You Yahoo!? Yahoo! Health - Feel bet

Re: Automake 1.6b available and the version numbering issue

2002-08-01 Thread Eric Siegerman
On Thu, Aug 01, 2002 at 11:48:00AM -0400, Respond To List Only wrote: > So, one comparison function for Automake, one for OpenSSL, one for the > next program, one for the next program... Again, creating upstream > problems for downstream users. Emphatically agreed. > > # For the purpose of orde

Re: how to disable ylwrap?

2002-08-01 Thread akim
On Thu, Aug 01, 2002 at 09:22:42AM -0700, John Millaway wrote: > > I don't think you can. However if you name your lexer `foo.ll' > > then Automake will build `foo.cc'. > > I can't believe there is no way to override this. ylwrap is a most frustrating > addition to automake. It's probably beca

Re: Beginner: a simple question about shared libraries

2002-08-01 Thread Ladislav Strojil
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 01 August 2002 17:50, Alexandre Duret-Lutz wrote: > Hi! > > >>> "Ladislav" == Ladislav Strojil <[EMAIL PROTECTED]> writes: > > [...] > > Ladislav> I am trying to move our school project to automake. > > What version of Automake? [lada@sm

Re: Beginner: a simple question about shared libraries

2002-08-01 Thread Alexandre Duret-Lutz
>>> "Ladislav" == Ladislav Strojil <[EMAIL PROTECTED]> writes: [...] Ladislav> [lada@smrz ~]$ automake --version Ladislav> automake (GNU automake) 1.5 Thanks. The current version is 1.6.3, could you try that? If it still doesn't work, could you send in your Makefile.am and the resulting Mak

Re: Automake 1.6b available and the version numbering issue

2002-08-01 Thread Alexandre Duret-Lutz
Hi Respond, >>> "Respond" == Respond To List Only <[EMAIL PROTECTED]> writes: Respond> Let me preface this with the comment that, although it Respond> may lok like I'm ranting on some small issue that Respond> suddenly pushed me into a fit of rage, I'm actually Respond> sanely trying to rais

Re: Automake 1.6b available.

2002-08-01 Thread Alexandre Duret-Lutz
>>> "Bob" == Bob Ham <[EMAIL PROTECTED]> writes: [...] Bob> Any idea when 1.7 will be released (roughly, obviously; I Bob> mean, months? weeks? days?) I've got a build tree in a Bob> cvs that uses cvs automake. It's waiting for 1.7 until Bob> it's committed :) CVS Automake needs Autocon

Re: Beginner: a simple question about shared libraries

2002-08-01 Thread Ladislav Strojil
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 01 August 2002 21:56, Alexandre Duret-Lutz wrote: > >>> "Ladislav" == Ladislav Strojil <[EMAIL PROTECTED]> writes: > > [...] > > Ladislav> [lada@smrz ~]$ automake --version > Ladislav> automake (GNU automake) 1.5 > > Thanks. The current