Yaakov (Cygwin Ports) wrote:
*) Most packages still use a 1.5 libtool, if not older. Is LT_OUTPUT
the default if the old-style AC_PROG_LIBTOOL macro is called?
No, it is not.
If it's
not, it should be, as I know of a number of packages which rely on the
libtool script during configure.
Th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chuck,
I have yet to try libtool 2.2, but I'm sure that you have thoroughly
tested it. Could you clarify a few things:
*) Most packages still use a 1.5 libtool, if not older. Is LT_OUTPUT
the default if the old-style AC_PROG_LIBTOOL macro is cal
It was in some mirrros, for example:
http://bo.mirror.garr.it/mirrors/sourceware.org/cygwin/release/gdb/
File: gdb-6.8-1-src.tar.bz2 12638 KB4/5/20082:10:00 AM
File: gdb-6.8-1.tar.bz2 4419 KB 4/5/20082:10:00 AM
so it must the the ini file.
--
Unsu
You're right, I couldn't find dgb-6.9.1 either.
Angelo Graziosi <[EMAIL PROTECTED]> wrote:
> Perhaps there is a problem with mirrors and/or setup.ini: the mirrors
> have the tarball but setup.ini does not contains references to
> gdb-6.8-1.
>
> Cheers,
>Angelo.
>
--
Unsubscribe info:
Perhaps there is a problem with mirrors and/or setup.ini: the mirrors
have the tarball but setup.ini does not contains references to gdb-6.8-1.
Cheers,
Angelo.
---
Facesti come quei che va di notte,
che porta il lume dietro e se' non giova,
ma dopo se' fa le persone dotte.
.
Great, I appreciate your efforts. This will be very helpful to us all.
-- Re:
Christopher Faylor <[EMAIL PROTECTED]> wrote:
> I've made a new version of the gdb debugger available for installation.
> This version is a refresh from the 6.8 branch of the CVS repository on
> sourceware.org.
GNU libtool is a generic library support script. Libtool hides the
complexity of using shared libraries behind a consistent, portable
interface.
This is a new major release, the first official cygwin release from the
upstream 2.2 branch. As such, this release announcement is rather wordy
-- but
After a few hours I tried to send this mail
'the prize we sought is won' !
As a workaround, perhaps we should
mv /usr/include/X11/Xft ..//X11R6/include/X11
and then reintall xorg-x11-devel.
Right?
Angelo.
---
O Captain! my Captain! our fearful trip is done,
The ship has weather'd every rack
Brian Dessent wrote:
Angelo Graziosi wrote:
and if cygport depend on libtool1.5, how can the user who needs
libtool2.2 install it without uninstalling libtool1.5+cygport+...?
I think cygport should remove its requires: libtoolx.y from its
setup.hint. It currently lists that because the defa
Perhaps there is a packaging bug.
After installing libXft*-2.1.7, 'cygcheck' says that
---
File type mismatch: /usr/include/X11 from package xorg-x11-devel
xorg-x11-devel 6.8.99.901-1 Incomplete
Now /usr/include/X11 is a directory containing Xft, instead in
xor
I am trying to flag a possible packaging bug in pakages uploaded today,
but I got always a failur notice.
This is almost a try.
Angelo.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin
On 02/04/2008, Corinna Vinschen <[EMAIL PROTECTED]> wrote:
> On Apr 2 10:56, Corinna Vinschen wrote:
> >
> > The above mentioned names are the old directory names used before Vista.
> > These names have changed, for instance, "Application Data" is now called
> > "AppData". The old names stil
On Sun, Apr 06, 2008 at 12:55:02PM +0900, wynfield wrote:
>Brian Dessent wrote:
>>Build gettext yourself if you want a newer version. This is FOSS,
>>you're not helpless.
>
>Brian, its known at times, that you make really lame statements, but
>the one above is beneath even you, I thought.
Actuall
On Sun, Apr 06, 2008 at 12:18:16PM -0700, Brian Dessent wrote:
>Chris Game wrote:
>>>I can assure you that many of us cross compile Cygwin on Linux
>>>regularly...
>>
>>Er, why?
>
>Because as I said it's significantly faster, and because the developers
>tend to have Linux machines around anyway bec
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andrew DeFaria wrote:
| Robert Pendell wrote:
|> I don't see this as a bug. The same behavior can be observed on a
|> NetBSD machine when Putty is closed using that method or if my
|> connection to the server drops. I usually have to log back in and
Chris Game wrote:
> > I can assure you that many of us cross compile Cygwin on Linux
> > regularly...
>
> Er, why?
Because as I said it's significantly faster, and because the developers
tend to have Linux machines around anyway because of
work/preference/etc.
Brian
--
Unsubscribe info: h
Robert Pendell wrote:
I don't see this as a bug. The same behavior can be observed on a
NetBSD machine when Putty is closed using that method or if my
connection to the server drops. I usually have to log back in and
check for processes that are still running from my previous session.
And yo
On Sat, 05 Apr 2008 00:29:06 -0700, Brian Dessent wrote:
> I can assure you that many of us cross compile Cygwin on Linux
> regularly...
Er, why?
--
Chris Game
If at first you don't succeed, call it version 1.0
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem report
18 matches
Mail list logo
