each other as compilation and
linking progress.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Kurt D. Zeilenga
> Sent: Monday, October 02, 2000 1:32 PM
> To: Howard Chu
> Cc: [EMAIL PROTECTED]
> Subject: RE: libtool up
Sorry, this message was not intended for the autoconf list. Meant to copy to
the libtool list.
> -Original Message-
> From: Howard Chu [mailto:[EMAIL PROTECTED]]
> Sent: Monday, October 02, 2000 1:54 PM
> To: Kurt D. Zeilenga; [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED
encies...
http://highlandsun.com/hyc/#Make
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
___
Autoconf mailin
I suppose this is really a question for the autoconf folks, as it
affects more in our configure scripts than just libtool.
Original Message
Subject: libtool AC_ARG_WITH and autoconf 2.59
Date: Wed, 24 Aug 2005 20:02:23 -0700
From: Howard Chu <[EMAIL PROTECTED]>
To: Libto
Stepan Kasal wrote:
Hello,
On Wed, Aug 24, 2005 at 08:17:40PM -0700, Howard Chu wrote:
reading the autoconf 2.59 document to see if there's a macro to control
this behavior,
no there is no documented way to change this. I think I could relatively
easily design a hack which would merg
That would be OK. Maybe AC_PRESERVE_HELP_ORDER instead, that might be
more clear.
--
-- Howard Chu
Chief Architect, Symas Corp. http://www.symas.com
Director, Highland Sunhttp://highlandsun.com/hyc
OpenLDAP Core Teamhttp://www.open
would change which one did.
That would be OK. Maybe AC_PRESERVE_HELP_ORDER instead, that might be
more clear.
--
-- Howard Chu
Chief Architect, Symas Corp. http://www.symas.com
Director, Highland Sunhttp://highlandsun.com/hyc
OpenLDAP Core Teamhttp://www.openlda
Howard Chu wrote:
Something like this seems to be pretty painless...
Of course I got the quoting wrong that time. This works for both cases.
--
-- Howard Chu
Chief Architect, Symas Corp. http://www.symas.com
Director, Highland Sunhttp://highlandsun.com/hyc
OpenLDAP Core Team
Howard Chu wrote:
Howard Chu wrote:
Something like this seems to be pretty painless...
Of course I got the quoting wrong that time. This works for both cases.
Sent the old diff twice, sheesh. This time for sure.
--
-- Howard Chu
Chief Architect, Symas Corp. http://www.symas.com
k for usleep() if setitimer doesn't exist? What about
nanosleep()? I expect many systems would need to realtime library
(-lrt) linked to use nanosleep()? Or not?
The tried-and-true method for the past 20-some years has been select()
with no descriptor sets...
--
-- Howard Chu
Chief
with some additional customization.
--
-- Howard Chu
Chief Architect, Symas Corp. http://www.symas.com
Director, Highland Sunhttp://highlandsun.com/hyc
OpenLDAP Core Teamhttp://www.openldap.org/project/
___
Autoconf mailing lis
antly faster than with Cygwin.
--
-- Howard Chu
Chief Architect, Symas Corp. http://www.symas.com
Director, Highland Sunhttp://highlandsun.com/hyc
OpenLDAP Core Teamhttp://www.openldap.org/project/
___
Autoconf mailing
ugh this exercise for the Mozilla codebase several months ago...
--
-- Howard Chu
Chief Architect, Symas Corp. http://www.symas.com
Director, Highland Sunhttp://highlandsun.com/hyc
OpenLDAP Core Teamhttp://www.openldap.org/project/
___
time but never bothered to sit down and think of
a permanent solution. I always wind up editing the relevant Makefiles
and changing
CFLAGS=-g -O2 ...
to
OPT=-g -O2
CFLAGS=$(OPT) ...
and running with "make OPT=-g" when I want a pure debug build.
--
-- Howard Chu
Chief Architect,
the
changes to the Makefiles.
--
-- Howard Chu
Chief Architect, Symas Corp. http://www.symas.com
Director, Highland Sunhttp://highlandsun.com/hyc
OpenLDAP Core Teamhttp://www.openldap.org/project/
___
Autoconf mailing list
d - for instance, when
I'm experimenting with something new.
Right; I pretty much never override CFLAGS itself, too much hassle to
get all of the other definitions.
--
-- Howard Chu
Chief Architect, Symas Corp. http://www.symas.com
Director, Highland Sunhttp://highla
As I recall when porting a number of packages to OS/390 and z/OS, all
of configure's conftests failed using "return" (SEGV) and I had to
change them all to "exit"...
--
-- Howard Chu
Chief Architect, Symas Corp. http://www.symas.com
Director, Highland Sun
Matthew Woehlke wrote:
Howard Chu wrote:
Paul Eggert wrote:
"Ilya N. Golubev" <[EMAIL PROTECTED]> writes:
Have no systems with broken `return' at hand,
That's the fundamental problem. These systems are _ancient_ -- they
all predate C89 -- and they are so old that
Ilya N. Golubev wrote:
As I understand it,
these are pre-1989 systems (or is it pre-1979?)
Looks like there is quite many systems called that. Some of them are
actually modern ones on top of native ibm system.
To Howard Chu: was system exhibiting that broken `return' a native ib
Howard Chu wrote:
Ilya N. Golubev wrote:
As I understand it,
these are pre-1989 systems (or is it pre-1979?)
Looks like there is quite many systems called that. Some of them are
actually modern ones on top of native ibm system.
To Howard Chu: was system exhibiting that broken `return
was with you up to the end. You should have no expectation that
anything compiled for the target can execute reasonably on the build
host in a cross-compiling environment.
As usual, I think just using MSYS is the best solution.
--
-- Howard Chu
Chief Architect, Symas Corp. http://www.syma
the source for bash and build/install
that. That would solve this initial problem, and let you move on to the
next...
--
-- Howard Chu
Chief Architect, Symas Corp. http://www.symas.com
Director, Highland Sunhttp://highlandsun.com/hyc
Chief Architect, OpenLDAP http://www.openldap
real effort for the
project maintainers to commit their generated files. It takes inordinate
effort for some other developer.
--
-- Howard Chu
Chief Architect, Symas Corp. http://www.symas.com
Director, Highland Sunhttp://highlandsun.com/hyc
Chief Architect, OpenLDAP http://www.
Ralf Wildenhues wrote:
Hello Howard,
* Howard Chu wrote on Mon, Feb 26, 2007 at 01:05:25PM CET:
I was thinking it might be a good idea for the autoconf/automake docs to
include suggested best practices for distributing source. Said practice
to include providing ready-to-run configure script
uffer caches, so coherence is implicitly maintained between mmap
and read/write.
Of course on Windows it's possible to intentionally break coherence by doing
an unbuffered write, which would make any cached copy of a page stale.
--
-- Howard Chu
CTO, Symas Corp. http://www.s
-ibm-aix7
> machines if I don't set XPG_SUS_ENV=ON.
>
> Finally, I got two failures I wasn't expecting to see at all:
>
> test: writes visible via shared map... FAIL: data mismatch
> test: shared map alterations visible via read... FAIL: data mismatch
> amd64
rn ESTALE if there had been a write (which INN then uses as a
> trigger to unmap and remap the file).
>
> Here too I have not revalidated this subsequently. This would have been
> in the days of NFSv3 (if not NFSv2 in places).
NFS and its interaction with caching layers is still a myster
27 matches
Mail list logo
