From: Milan Zamazal <pdm@zamazal.org>
To: Lars Henriksen <Lars.Henriksen@netman.dk>
Cc: help-gnats@gnu.org, Yngve Svendsen <yngve.svendsen@clustra.com>
Subject: Re: libiberty and regex.* updated
Date: Fri, 02 Nov 2001 05:55:00 -0000 [thread overview]
Message-ID: <87zo4ojfb9.fsf@blackbird.zamazal.org> (raw)
In-Reply-To: <20011212180122.F14246@cisws11.netman.dk>
>>>>> "YS" == Yngve Svendsen <yngve.svendsen@clustra.com> writes:
YS> Got the following when compiling on Sun Solaris 7 with GCC 2.95.2:
YS> #gmake all
YS> gmake -C libiberty
YS> gmake[1]: Entering directory `/usr/local/src/gnats-1200/gnats/libiberty'
YS> if [ x"" != x ] && [ ! -d pic ]; then \
YS> mkdir pic; \
YS> else true; fi
YS> touch stamp-picdir
YS> gmake[1]: *** No rule to make target `include/libiberty.h', needed by `argv.o'.
YS> Stop.
YS> gmake[1]: Leaving directory `/usr/local/src/gnats-1200/gnats/libiberty'
YS> gmake: *** [libiberty/libiberty.a] Error 2
>>>>> "LH" == Lars Henriksen <Lars.Henriksen@netman.dk> writes:
LH> Same result on Compaq Tru64 UNIX (OSF1) 5.1 with GCC 3.0.2.
Have you run your `cvs update' with the `-d' option? There is a new
`include' subdirectory in `libiberty/'.
Regards,
Milan Zamazal
--
And why?
_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://mail.gnu.org/mailman/listinfo/help-gnats
WARNING: multiple messages have this Message-ID
From: Milan Zamazal <pdm@zamazal.org>
To: Lars Henriksen <Lars.Henriksen@netman.dk>
Cc: help-gnats@gnu.org, Yngve Svendsen <yngve.svendsen@clustra.com>
Subject: Re: libiberty and regex.* updated
Date: Wed, 12 Dec 2001 15:06:00 -0000 [thread overview]
Message-ID: <87zo4ojfb9.fsf@blackbird.zamazal.org> (raw)
Message-ID: <20011212150600.sz9G8Mg7FzGFL0sCm_6Z-nVpDUXQamOkuSp7gEPMtT4@z> (raw)
In-Reply-To: <20011212180122.F14246@cisws11.netman.dk>
>>>>> "YS" == Yngve Svendsen <yngve.svendsen@clustra.com> writes:
YS> Got the following when compiling on Sun Solaris 7 with GCC 2.95.2:
YS> #gmake all
YS> gmake -C libiberty
YS> gmake[1]: Entering directory `/usr/local/src/gnats-1200/gnats/libiberty'
YS> if [ x"" != x ] && [ ! -d pic ]; then \
YS> mkdir pic; \
YS> else true; fi
YS> touch stamp-picdir
YS> gmake[1]: *** No rule to make target `include/libiberty.h', needed by `argv.o'.
YS> Stop.
YS> gmake[1]: Leaving directory `/usr/local/src/gnats-1200/gnats/libiberty'
YS> gmake: *** [libiberty/libiberty.a] Error 2
>>>>> "LH" == Lars Henriksen <Lars.Henriksen@netman.dk> writes:
LH> Same result on Compaq Tru64 UNIX (OSF1) 5.1 with GCC 3.0.2.
Have you run your `cvs update' with the `-d' option? There is a new
`include' subdirectory in `libiberty/'.
Regards,
Milan Zamazal
--
And why?
_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://mail.gnu.org/mailman/listinfo/help-gnats
next prev parent reply other threads:[~2001-12-12 23:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-30 15:34 Milan Zamazal
2001-11-01 7:14 ` Yngve Svendsen
2001-11-01 14:02 ` Lars Henriksen
2001-11-02 5:55 ` Milan Zamazal [this message]
2001-11-02 6:05 ` Lars Henriksen
2001-12-13 0:54 ` Lars Henriksen
2001-12-12 15:06 ` Milan Zamazal
2001-12-12 9:06 ` Lars Henriksen
2001-12-11 15:28 ` Yngve Svendsen
2001-12-11 7:58 ` Milan Zamazal
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=87zo4ojfb9.fsf@blackbird.zamazal.org \
--to=pdm@zamazal.org \
--cc=Lars.Henriksen@netman.dk \
--cc=help-gnats@gnu.org \
--cc=yngve.svendsen@clustra.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).