On Sun, Jul 14, 2002 at 09:57:07PM +0200, Ralf Habacker wrote:
>Ralf Habacker wrote:
>>>By hand, because sourceforge does not allow any subdirs in the download
>>>area, so upset and other scripts are not usable:-(
upset doesn't rely on subdirs.
cgf
>
>
>This may be a solution, but isn't upset a perl script ? Currently that may be a
>little problem for me because I'm not a perl expert, but I will take a look.
>
>
Well you just could use "upset" an then a simple sed script, someling like
/directory\\//g, to remove the "directory/" in front
Hallo,
expat-1.95.3 was buggy and is no longer available at sourceforge,
so please do delete the Cygwin release too.
There is a bugfix release available instead of 1.95.3, this is
1.95.4:
http://familiehaase.de/cywgin/expat/expat-1.95.4-1.tar.bz2
http://familiehaase.de/cywgin/expat/expat-1.9
Ralf Habacker wrote:
>
> >>Who is creating kde's setup.ini? Are they writing it by hand,
> >>
> >
> >By hand, because sourceforge does not allow any subdirs in the
> download area, so
> >upset and other scripts are not usable:-(
> >
> Why don't you ASK them to allow you to create folders.
> Expla
Lapo Luchini wrote:
>> You should either
>> 1) change mkpatch() to only create a diff between your populated
>> libungif-4.1.0\CYGWIN-PATCHES directory and an empty
>> libungif-4.1.0-orig\CYGWIN-PATCHES, and keep the "aclocal &&
>> libtoolize --force" command in conf(), or
>> 2) Lapo run
> Also, it should probably be "aclocal && libtoolize --force --copy &&
> automake --gnu --copy --add-missing --force-missing && autoconf" but
> that's just me.
>
>> This time it uses no patch but a simple "aclocal && libtoolize
>> --force" in the "conf" phase.
>
OK, I'll do some search to unde
> You should either
> 1) change mkpatch() to only create a diff between your populated
> libungif-4.1.0\CYGWIN-PATCHES directory and an empty
> libungif-4.1.0-orig\CYGWIN-PATCHES, and keep the "aclocal &&
> libtoolize --force" command in conf(), or
> 2) Lapo runs "aclocal && libtoolize --fo
Nicholas Wourms wrote:
>
> A) FWICT, he isn't running autoheader/automake/autoconf, which means
> configure is not being regenrated.
Yes, I pointed that out in another message.
>
> B)He could try adding AC_LIBTOOL_WIN32_DLL right before AM_PROG_LIBTOOL
> in configure.in, which should tel
Lapo Luchini wrote:
>
> ...but I used method two to package it, so people usn't using
> "./configure; make", just "./libungif-4.1.0-2.sh all" and as I have
> modificed the script himself, nothing changes to people.
> In my point of view requiring installed packages is better than
> including
This one seems okay to me. There is one minor discrepancy:
If you run 'libungif-4.1.0-2.sh all' you do NOT get the same -src package...
This is because the mkpatch() procedure will generate a very large patch
which if applied to a pristine source directory will make it unnecessary
to run "acl
Charles Wilson wrote:
>
>
> Lapo Luchini wrote:
>
>>> BTW, you can also relibtoolize glib (and probably gtk) in a similar
>>> way.
>>
>>
>>
>> Uhm.. I had no problem relibtoolizing libungif, but I indeed have
>> problems with glib:
>> ltconf part of confgiure says:
>>
>> checking if libtool sup
>
>
>> Problem is.. what is libtool? 0=)
>> Well one of the reasons why I work on cygwin is just to learn... I
>> guess it is time to do some google:libtool and go finding a
>> FAQ/manual about it
>> (grrr, www.gnu.org is down... I hope libtool manual's mirror at
>> www.delorie.com is fresh eno
Lapo Luchini wrote:
>> Steven's 'mkdll.sh' script is just plain wrong. libungif is a
>> libtoolized package, you should just relibtoolize.
>
>
> Problem is.. what is libtool? 0=)
> Well one of the reasons why I work on cygwin is just to learn... I guess
> it is time to do some google:libt
Robert Collins wrote:
>Nicholas, check your yahoo account, I emailed you there hours ago.
>
>Thank you for the stack dump it will likely help. Where on the screen
>did you click - beside the 'all' category / on a specific package?
>
>
>Rob
>
>
>>-Original Message-
>>From: Nicholas Wourms
Ralf Habacker wrote:
>>Who is creating kde's setup.ini? Are they writing it by hand,
>>
>
>By hand, because sourceforge does not allow any subdirs in the download area, so
>upset and other scripts are not usable:-(
>
Why don't you ASK them to allow you to create folders. Explain why you
need t
Lapo Luchini wrote:
>> BTW, you can also relibtoolize glib (and probably gtk) in a similar way.
>
>
> Uhm.. I had no problem relibtoolizing libungif, but I indeed have
> problems with glib:
> ltconf part of confgiure says:
>
> checking if libtool supports shared libraries... yes
> checking
Nicholas, check your yahoo account, I emailed you there hours ago.
Thank you for the stack dump it will likely help. Where on the screen
did you click - beside the 'all' category / on a specific package?
Rob
> -Original Message-
> From: Nicholas Wourms [mailto:[EMAIL PROTECTED]]
> Sen
Robert Collins wrote:
>If you run setup under DebugView, or a similar tool, is any output
>created?
>Can you get me a stackdump?
>
>Rob
>
>
>>-Original Message-
>>From: [EMAIL PROTECTED]
>>[mailto:[EMAIL PROTECTED]] On Behalf Of Nicholas Wourms
>>Sent: Sunday, 14 July 2002 8:46 AM
>>To:
> Who is creating kde's setup.ini? Are they writing it by hand,
By hand, because sourceforge does not allow any subdirs in the download area, so
upset and other scripts are not usable:-(
> If the former, then the human who wrote it is WRONG. the package name
> for the file 'kde-x-1.3.tar.bz2'
> BTW, you can also relibtoolize glib (and probably gtk) in a similar way.
Uhm.. I had no problem relibtoolizing libungif, but I indeed have
problems with glib:
ltconf part of confgiure says:
checking if libtool supports shared libraries... yes
checking if package supports dlls... no
checking w
Libungif: a library for using uncompressed GIFs.
This time it uses no patch but a simple "aclocal && libtoolize --force"
in the "conf" phase.
(binary package is bigger because I also included the "doc" subdirectory
in the install, or else people with only binary would have no help on
commands
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]] On Behalf Of Lapo Luchini
> Sent: Sunday, 14 July 2002 7:44 PM
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]:CygWin-Apps
> OK, I prepared the package using "aclocal && libtoolize
> --force" at the
> beginning of
> Steven's 'mkdll.sh' script is just plain wrong. libungif is a
> libtoolized package, you should just relibtoolize.
Problem is.. what is libtool? 0=)
Well one of the reasons why I work on cygwin is just to learn... I guess
it is time to do some google:libtool and go finding a FAQ/manual abou
23 matches
Mail list logo
