From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: <gdb@sourceware.org>
Subject: gdb/gnulib problems with BSD operating systems
Date: Thu, 29 Mar 2012 14:27:00 -0000 [thread overview]
Message-ID: <000301cd0db8$1178b7c0$346a2740$@muller@ics-cnrs.unistra.fr> (raw)
I tried to compile gdb (7.4 release and current CVS)
on openbsd/netbsd/freebsd systems
(with i386 cpus, but this is probably not relevant).
I get into the same problem for all three systems:
gmake all-gdb
fails in
build/gdb/gnulib
This seems to come from the fact that
build/gdb/gnulib/Makefile
contains a line with
MAKE = make
so that despite being calls from gmake,
it calls BSD style make executable
that doesn't know how to handle some GNU specific stuff.
Changing the line in
build/gdb/gnulib/Makefile
to
MAKE = gmake
is enough to allow me to complete compilation of GDB
successfully, but I was wondering if there is not some
error somewhere.
I tried to do a global configure for which I added
an explicit
../src/configure MAKE=gmake
but even this wasn't able to get the correct value into
build/gdb/gnulib/Makefile
Is this an error in the configure script of GDB,
or should I specify which make I intent to use
differently?
Pierre Muller
GDB pascal language maintainer
next reply other threads:[~2012-03-29 14:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-29 14:27 Pierre Muller [this message]
2012-03-29 16:21 ` Joel Brobecker
[not found] <32726.6318876811$1333031278@news.gmane.org>
2012-03-30 20:35 ` Tom Tromey
2012-03-30 21:35 ` Joel Brobecker
2012-03-30 22:07 ` Joel Brobecker
2012-03-31 12:08 ` Pierre Muller
2012-03-31 18:17 ` Pierre Muller
[not found] ` <24504.7532058836$1333217860@news.gmane.org>
2012-04-02 14:18 ` Tom Tromey
2012-04-05 9:44 ` Pierre Muller
2012-04-10 15:05 ` Joel Brobecker
[not found] ` <37068.5830399909$1333195740@news.gmane.org>
2012-04-02 14:17 ` Tom Tromey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000301cd0db8$1178b7c0$346a2740$@muller@ics-cnrs.unistra.fr' \
--to=pierre.muller@ics-cnrs.unistra.fr \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).