In article <[EMAIL PROTECTED]>, Sam Steingold <[EMAIL PROTECTED]> wrote:
>Berkley db changed prototypes for functions that are struct members.
>how do I check for that?
The official word from Sleepycat is that it's much better to statically
link against a known version of BDB that you ship with y
ions but no
>response...
./configure CFLAGS=-O
However, in general, you want -g.
mrc
--
Mike Castle [EMAIL PROTECTED] www.netcom.com/~dalgoda/
We are all of us living in the shadow of Manhattan. -- Watchmen
fatal ("You are in a maze of twisty compiler features, all different"); -- gcc
--with-crypt=[gcrypt|crypto] ?
mrc
--
Mike Castle [EMAIL PROTECTED] www.netcom.com/~dalgoda/
We are all of us living in the shadow of Manhattan. -- Watchmen
fatal ("You are in a maze of twisty compiler features, all different"); -- gcc
l true, but I think the same issue _could_
happen with any vendors installed autoconf.
mrc
--
Mike Castle [EMAIL PROTECTED] www.netcom.com/~dalgoda/
We are all of us living in the shadow of Manhattan. -- Watchmen
fatal ("You are in a maze of twisty compiler features, all different"); -- gcc
In article <[EMAIL PROTECTED]>,
Russ Allbery <[EMAIL PROTECTED]> wrote:
>Mike Castle <[EMAIL PROTECTED]> writes:
>> When building from source, one rarely changes needs to make patches to
>> configure.{in,ac} and then run autotools*.
>
>That depends on
27;re using known versions of libc,
binutils, gcc, rather than whatever may be installed on the system. Apply
the same to autoconf.
mrc
--
Mike Castle [EMAIL PROTECTED] www.netcom.com/~dalgoda/
We are all of us living in the shadow of Manhattan. -- Watchmen
fatal ("You are in a maze of twisty compiler features, all different"); -- gcc
ocated in /usr/local/lib, then indeed this is a bad
sign. In that case, you'll probably be better off asking for help in a
Linux specific discussion area (or pester a local guru).
Good luck,
mrc
--
Mike Castle [EMAIL PROTECTED] www.netcom.com/~dalgoda/
We are all of us
>another before the library
Is /usr/local/lib in /etc/ld.so.conf ?
Do your tests for the existence of libgsl just compile or does it run as
well? If it doesn't run, that could explain the situation here.
mrc
--
Mike Castle [EMAIL PROTECTED] www.netcom.com/~dalgoda/
We are
I see that a lot of packages (bison, for example) use AC_INCLUDES_DEFAULT.
Yet, this isn't documented anywhere.
Should maintainers be using AC_INCLUDES_DEFAULT? If so, should they be
using AC_INCLUDES_DEFAULT or $ac_includes_default. And, should it be
documented?
mrc
--
Mike C
In article <[EMAIL PROTECTED]>,
Mike Castle <[EMAIL PROTECTED]> wrote:
>Ok. Strange interactions with autoscan and autom4te.cache. And a possible
>bug in autoscan otherwise.
Hmmm. The following patch seems to improve my system a little bit. But
I'm not certain if t
[sys_siglist])
nexus@thune[10:07pm]~/foo(215) autoscan -V
autoscan (GNU Autoconf) 2.57
Written by David J. MacKenzie and Akim Demaille.
So, why different results after nuking autom4te.cache? Also, why is it
bitching about sys_siglist?
Thanks,
mrc
--
Mike Castle [EMAIL PROTECTED]
on you.
Hint: IT should not be involved in updating your autoconf stuff. Your
developers and configuration manager should be.
mrc
--
Mike Castle [EMAIL PROTECTED] www.netcom.com/~dalgoda/
We are all of us living in the shadow of Manhattan. -- Watchmen
fatal ("You are in a
r
API to have have functions that provides those values at runtime.
mrc
--
Mike Castle [EMAIL PROTECTED] www.netcom.com/~dalgoda/
We are all of us living in the shadow of Manhattan. -- Watchmen
fatal ("You are in a maze of twisty compiler features, all different"); -- gcc
k away from autoconf and write a meta program that
will generate configure.in for you.
mrc
--
Mike Castle [EMAIL PROTECTED] www.netcom.com/~dalgoda/
We are all of us living in the shadow of Manhattan. -- Watchmen
fatal ("You are in a maze of twisty compiler features, all different"); -- gcc
On Thu, Oct 04, 2001 at 11:52:03AM -0700, Paul Eggert wrote:
> > From: Mike Castle <[EMAIL PROTECTED]>
> > I didn't realize that DOS and NT were considered UNIX-like systems.
> [deleted]
> My understanding is that bare DOS is not UNIX-like, but it gets
> reason
On Wed, Oct 03, 2001 at 11:52:11PM -0700, Paul Eggert wrote:
> Autoconf is merely a tool for configuring source code for UNIX-like
> systems. That problem is hard enough.
I didn't realize that DOS and NT were considered UNIX-like systems.
mrc
--
Mike Castle [EMAI
in
supporting poor programming.
mrc
--
Mike Castle [EMAIL PROTECTED] www.netcom.com/~dalgoda/
We are all of us living in the shadow of Manhattan. -- Watchmen
fatal ("You are in a maze of twisty compiler features, all different"); -- gcc
On Thu, May 24, 2001 at 11:37:22AM +0200, Peter Eisentraut wrote:
> Mike Castle writes:
> > How do you reference the generated make file?
>
> include $(top_builddir)/Makefile.global
>
> This requires that you set top_builddir somewhere.
Well, that's the magic I was w
I'm thinking about problems building outside of the source tree.
mrc
--
Mike Castle Life is like a clock: You can work constantly
[EMAIL PROTECTED] and be right all the time, or not work at all
www.netcom.com/~dalgoda/ and be right at least twice a day. -- mrc
We are
re of this stuff last night.]
mrc
--
Mike Castle Life is like a clock: You can work constantly
[EMAIL PROTECTED] and be right all the time, or not work at all
www.netcom.com/~dalgoda/ and be right at least twice a day. -- mrc
We are all of us living in the shadow of Manhattan. -- Watchmen
id sites get put onto blocks.
Do you block rate limited open relays that are useless for spammers?
Do you block sites that prevent you from testing for open relays? (This
probably falls under the "proven" clause by examining past history only; no
proactive work.)
mrc
--
Mike C
On Tue, Mar 06, 2001 at 05:51:45PM +0100, Assar Westerlund wrote:
> Mike Castle <[EMAIL PROTECTED]> writes:
> > NT. (NT will happily rename() across disks, hardly an atomic operation).
>
> What rename() is that? It's not the one in their posix library I
> assume?
for performance reasons, rename
was not made atomic).
mrc
--
Mike Castle Life is like a clock: You can work constantly
[EMAIL PROTECTED] and be right all the time, or not work at all
www.netcom.com/~dalgoda/ and be right at least twice a day. -- mrc
We are all of us living
On Tue, Sep 12, 2000 at 01:01:09PM -0400, Pavel Roskin wrote:
> I believe it would be more constructive to make M$VC accept .cc extention
> is some non-interactive way. Anybody knows how?
$(CP) foo.cc foo.cpp
$(CC) foo.cpp
?
mrc
--
Mike Castle Life is like a clock: You ca
; remembering to do so every time you update them, it's easier to just
> link them statically.
Also, if an upgrade goes bad and /lib gets hosed (running out of disk
space for instance), you're possibly stuck with an unusuable system.
mrc
--
Mike Castle Life is like a clock
loping code/bug hunting, and you want to build for, say
/usr/local/test instead of /usr/local.
mrc
--
Mike Castle Life is like a clock: You can work constantly
[EMAIL PROTECTED] and be right all the time, or not work at all
www.netcom.com/~dalgoda/ and be right at least twice a d
, but neither string is found
in the body. Won't that still give you a false answer?
Of course, I'd argue that programs should be written so that endianness
doesn't matter.
mrc
--
Mike Castle Life is like a clock: You can work constantly
[EMAIL PROTECTED] and be ri
type... i386-pc-linux-gnu
checking host system type... i386-pc-linux-gnu
checking target system type... i386-pc-linux-gnu
--
Mike Castle Life is like a clock: You can work constantly
[EMAIL PROTECTED] and be right all the time, or not work at all
www.netcom.com/~dalgoda/ and be
.)'
So I guess this is an improvement. One problem at a time.
However, I must say, I do NOT like it changing "i386-linux" to
"i386-pc-linux-gnu". That is not what I typed in. If I want to override
it, I want to damn well override it.
mrc
On Mon, Jun 26, 2000 a
s the host system.
So, the non-option method of specifying the build system is no longer
supported?
If so, I'd have to say, this kinda sucks.
I have a bunch of scripts that I use to build packages that I will have to
change. Not to mention, it goes against the history of autoconf, and all
30 matches
Mail list logo
