e I kept
needing this functionality elsewhere.
You give it argv[0], BINDIR, and OTHERDIR; it computes the relative
path between bindir and otherdir, finds your application in $PATH or
similar, and works out the likely location of otherdir.
--
Daniel Jacobowitz
___
Autoconf mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/autoconf
ions for the GCC subdirectory.
--
Daniel Jacobowitz
CodeSourcery, LLC
___
Autoconf mailing list
Autoconf@gnu.org
http://lists.gnu.org/mailman/listinfo/autoconf
On Mon, Dec 02, 2002 at 02:39:49PM -0200, Alexandre Oliva wrote:
> On Dec 2, 2002, Daniel Jacobowitz <[EMAIL PROTECTED]> wrote:
>
> > You may already know this, but just to be careful I'll mention it
> > anyway... it is not necessarily safe to configure more than o
e
> may have to handle that especially, like autoconf does.
Yeah, I think this would be the way to go; but in any case, I suggest
that we serialize configure targets if it's practical to do so.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
On Sun, Sep 07, 2003 at 02:07:51PM -0400, Daniel Jacobowitz wrote:
> On HP/UX, including drags in a lot of other headers. With
> _HPUX_SOURCE defined, this includes a prototype for clock, which causes
> AC_CHECK_FUNCS(clock) to not find clock. The __stub macros are glibc
> spec
cludes a prototype for clock, which causes
AC_CHECK_FUNCS(clock) to not find clock. The __stub macros are glibc
specific, aren't they?
I don't have good patches for either issue. Checking for _HPUX_SOURCE to
defeat the __stub check is good enough for our purposes, so that's what
we
On Sun, Sep 07, 2003 at 02:07:51PM -0400, Daniel Jacobowitz wrote:
> Hi autoconf'ers...
>
> I've been involved in converting a number of projects in the GCC and sources
> (binutils, gdb, etc) repositories to autoconf 2.57. By and large, it's
> going well, but we
On Thu, Sep 11, 2003 at 10:06:21PM -0700, Paul Eggert wrote:
> Daniel Jacobowitz <[EMAIL PROTECTED]> writes:
>
> > However, that's not the whole story. The old check also failed if there
> > were warning messages on stderr when preprocessing. The new one do
On Fri, Sep 12, 2003 at 10:32:06AM -0700, Paul Eggert wrote:
> Daniel Jacobowitz <[EMAIL PROTECTED]> writes:
>
> > GCC is built (in bootstrap mode at least, where we know the compiler
> > will be GCC) using -Werror.
>
> OK. Then it should be configured with -Werror
On Fri, Sep 12, 2003 at 01:43:19PM -0700, Paul Eggert wrote:
> Daniel Jacobowitz <[EMAIL PROTECTED]> writes:
>
> > It happens that libiberty does
> > not use -Werror, and is always configured first, so _that_ finds
> > malloc.h.
>
> Can you arrange for libiber
On Fri, Sep 12, 2003 at 03:08:19PM -0700, Paul Eggert wrote:
> Daniel Jacobowitz <[EMAIL PROTECTED]> writes:
>
> > I think the easiest way for me to do this is simply to locally reset
> > the warnings-are-errors flag for AC_PREPROC_IFELSE. I don't suppose
> >
On Mon, Sep 15, 2003 at 10:42:16PM -0400, Daniel Jacobowitz wrote:
> On Fri, Sep 12, 2003 at 03:08:19PM -0700, Paul Eggert wrote:
> > Daniel Jacobowitz <[EMAIL PROTECTED]> writes:
> >
> > > I think the easiest way for me to do this is simply to locally reset
> >
On Tue, Sep 23, 2003 at 04:09:17PM -0700, Paul Eggert wrote:
> Daniel Jacobowitz <[EMAIL PROTECTED]> writes:
>
> > I need to settle on a solution to use in GCC until an updated
> > autoconf is available.
>
> Thanks. Your change good to me, so I installed it. I doc
you'll get only
three bits of permission instead of the usual nine. Personally, I'd
just mark everything executable if test -x didn't work.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
figure.in|ac so delete
> > acconfig.h] )], )
> > It didn't work.
>
> You can also prevent m4 from recognizing macros by inserting arbitrary
> quotes into the names. For instance AH_TEM[]PLATE or AH_T[EMP]LATE.
I believe the currently preferred way to do this is AH@&[EMAIL PROTECTED]
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
the backslashes. POSIX appears to allow this behavior. Using here
documents works:
$ cat < $a
> EOF
a\b
$
I don't know if ash is considered an unsuitable shell. I know Debian
used to allow it to be used as /bin/sh and no longer does.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
'/'''/g"` ;;
esac
So subdirs get corrupted --program-transform-name. There are plenty of
other instances, even this jewel with a wildly incorrect comment:
# Double any \ or $. echo might interpret backslashes.
# By default was `s,x,x', remove it if useless.
cat <<\_ACEOF >conftest.sed
s/[\\$]/&&/g;s/;s,x,x,$//
_ACEOF
program_transform_name=`echo $program_transform_name | sed -f conftest.sed`
rm conftest.sed
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
On Thu, Feb 12, 2004 at 10:29:29AM -0800, Paul Eggert wrote:
> Daniel Jacobowitz <[EMAIL PROTECTED]> writes:
>
> > > $ a='a\b'
> > > $ expr "X$a" : 'X\(.*\)'
> > > a\b
> >
> > That's a neat trick, I didn'
hat because build=host, it
> can run the output of the C compiler.
But this is incorrect. You don't shift by one; you shift target into
host, but build should stay the same. How can you expect configure to
work right if you lie to it about the build host?
--
Daniel Jacobowitz
19 matches
Mail list logo
