From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Pierre Muller'" <pierre.muller@ics-cnrs.unistra.fr>,
"'Joel Brobecker'" <brobecker@adacore.com>,
"'Tom Tromey'" <tromey@redhat.com>
Cc: <gdb@sourceware.org>
Subject: RE: gdb/gnulib problems with BSD operating systems
Date: Sat, 31 Mar 2012 18:17:00 -0000 [thread overview]
Message-ID: <003d01cd0f6a$6d4c0120$47e40360$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <002101cd0f36$ee5b8bc0$cb12a340$@muller@ics-cnrs.unistra.fr>
> > % /path/to/gdb/configure
> > % /home/brobecke/gmake
> >
I was wondering if the fact of
adding a full path could have an influence.
So I tested 4 variants (on GDB-7.4 sources)
Variant 1) Using just 'gmake'
Variant 2) Using '/usr/local/bin/gmake'
Variant 3) Using 'gmake all-gdb'
Variant 4) Using '/usr/local/bin/gmake all-gdb'
Clearly, only variants 1 and 2 complete successfully,
while variants using all-gdb
do have
MAKE = make
instead of
MAKE = 'gmake as called, i.e. with or without path'
There are differences in the gdb/Makefile's (see below)
but I have no idea if this explains the
failure with all-gdb target.
Pierre Muller
GDB pascal language maintainer
[pierre@freelove832 ~]$ diff -c test-gmake/gdb/Makefile
test-gmake-all-gdb/gdb/Makefile
*** test-gmake/gdb/Makefile Sat Mar 31 08:38:04 2012
--- test-gmake-all-gdb/gdb/Makefile Sat Mar 31 08:43:46 2012
***************
*** 55,62 ****
LN_S = ln -s
INSTALL = /usr/bin/install -c
! INSTALL_PROGRAM = /usr/bin/install -c
! INSTALL_DATA = /usr/bin/install -c -m 644
DESTDIR =
--- 55,62 ----
LN_S = ln -s
INSTALL = /usr/bin/install -c
! INSTALL_PROGRAM = ${INSTALL}
! INSTALL_DATA = ${INSTALL} -m 644
DESTDIR =
***************
*** 107,113 ****
YLWRAP = $(srcdir)/../ylwrap
# where to find makeinfo, preferably one designed for texinfo-2
! MAKEINFO = makeinfo --split-size=5000000
MAKEINFOFLAGS = --split-size=5000000
MAKEINFO_EXTRA_FLAGS =
MAKEINFO_CMD = $(MAKEINFO) $(MAKEINFOFLAGS) $(MAKEINFO_EXTRA_FLAGS)
--- 107,113 ----
YLWRAP = $(srcdir)/../ylwrap
# where to find makeinfo, preferably one designed for texinfo-2
! MAKEINFO = makeinfo
MAKEINFOFLAGS = --split-size=5000000
MAKEINFO_EXTRA_FLAGS =
MAKEINFO_CMD = $(MAKEINFO) $(MAKEINFOFLAGS) $(MAKEINFO_EXTRA_FLAGS)
***************
*** 2197,2217 ****
# simpler scheme.
#
! ifeq ($(DEPMODE),depmode=gcc3)
# Note that we put the dependencies into a .Tpo file, then move them
# into place if the compile succeeds. We need this because gcc does
# not atomically write the dependency output file.
! override COMPILE.post = -c -o $@ -MT $@ -MMD -MP \
! -MF $(DEPDIR)/$(basename $(@F)).Tpo
! override POSTCOMPILE = @mv $(DEPDIR)/$(basename $(@F)).Tpo \
! $(DEPDIR)/$(basename $(@F)).Po
! else
! override COMPILE.pre = source='$<' object='$@' libtool=no \
! DEPDIR=$(DEPDIR) $(DEPMODE) $(depcomp) $(CC)
# depcomp handles atomicity for us, so we don't need a postcompile
# step.
! override POSTCOMPILE =
! endif
# A list of all the objects we might care about in this build, for
# dependency tracking.
--- 2197,2217 ----
# simpler scheme.
#
! #ifeq ($(DEPMODE),depmode=gcc3)
# Note that we put the dependencies into a .Tpo file, then move them
# into place if the compile succeeds. We need this because gcc does
# not atomically write the dependency output file.
! #override COMPILE.post = -c -o $@ -MT $@ -MMD -MP \
! # -MF $(DEPDIR)/$(basename $(@F)).Tpo
! #override POSTCOMPILE = @mv $(DEPDIR)/$(basename $(@F)).Tpo \
! # $(DEPDIR)/$(basename $(@F)).Po
! #else
! #override COMPILE.pre = source='$<' object='$@' libtool=no \
! # DEPDIR=$(DEPDIR) $(DEPMODE) $(depcomp) $(CC)
# depcomp handles atomicity for us, so we don't need a postcompile
# step.
! #override POSTCOMPILE =
! #endif
# A list of all the objects we might care about in this build, for
# dependency tracking.
***************
*** 2221,2233 ****
# Ensure that generated files are created early. Use order-only
# dependencies if available. They require GNU make 3.80 or newer,
# and the .VARIABLES variable was introduced at the same time.
! ifdef .VARIABLES
! $(all_object_files): | $(generated_files)
! else
$(all_object_files) : $(generated_files)
! endif
# Dependencies.
! -include $(patsubst %.o, $(DEPDIR)/%.Po, $(all_object_files))
### end of the gdb Makefile.in.
--- 2221,2233 ----
# Ensure that generated files are created early. Use order-only
# dependencies if available. They require GNU make 3.80 or newer,
# and the .VARIABLES variable was introduced at the same time.
! #ifdef .VARIABLES
! #$(all_object_files): | $(generated_files)
! #else
$(all_object_files) : $(generated_files)
! #endif
# Dependencies.
! #-include $(patsubst %.o, $(DEPDIR)/%.Po, $(all_object_files))
### end of the gdb Makefile.in.
next prev parent reply other threads:[~2012-03-31 18:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
[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
2012-03-29 14:27 Pierre Muller
2012-03-29 16:21 ` Joel Brobecker
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='003d01cd0f6a$6d4c0120$47e40360$@muller@ics-cnrs.unistra.fr' \
--to=pierre.muller@ics-cnrs.unistra.fr \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=tromey@redhat.com \
/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).