From: Jeffrey A Law <law@cygnus.com>
To: Theodore Papadopoulo <Theodore.Papadopoulo@sophia.inria.fr>
Cc: egcs@cygnus.com
Subject: Re: New texinfo
Date: Fri, 27 Mar 1998 15:18:00 -0000 [thread overview]
Message-ID: <6467.890927630@hurl.cygnus.com> (raw)
In-Reply-To: <199803251107.MAA01068@mururoa.inria.fr>
In message < 199803251107.MAA01068@mururoa.inria.fr >you write:
>
> Am I the only one to experience problems with texinfo while trying to
> compile egcs from the CVS source tree (updated 03/25).
>
> configure complains it does not find ../egcs/texinfo/intl/libgettext.h and
> po files.
>
> Its seems that those sub-directories are not registered with cvs.
>
> I copied those files from the regular texinfo-3.12 distribution and
> now get:
>
> mururoa->../egcs/configure --prefix=/u/corse/2/robotvis/egcs --srcdir=../eg
> cs
> Configuring for a sparc-sun-solaris2.5.1 host.
> Created "Makefile" in /u/hawai/0/robotvis/papadop/src/egcs-solaris using "m
> h-frag"
> ./config.status is unchanged
> ../../egcs/texinfo/configure: EGCS_PROG_INSTALL: not found
> ../../egcs/texinfo/configure: AM_MAINTAINER_MODE: not found
> ../../egcs/texinfo/configure: AM_EXEEXT: not found
> ../../egcs/texinfo/configure: intl/po2tbl.sed: cannot create
> Links are now set up to build a native compiler for sparc-sun-solaris2.5.1
>
> Do I miss something ???
I believe I've fixed the autoconf problems.
jeff
next prev parent reply other threads:[~1998-03-27 15:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-25 4:47 Theodore Papadopoulo
1998-03-27 4:21 ` Manfred Hollstein
1998-03-27 15:18 ` H.J. Lu
1998-03-31 0:46 ` Jeffrey A Law
1998-03-27 15:18 ` Jeffrey A Law [this message]
[not found] <199803251107.MAA01068.cygnus.egcs@mururoa.inria.fr>
1998-03-26 21:54 ` Ulrich Drepper
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=6467.890927630@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=Theodore.Papadopoulo@sophia.inria.fr \
--cc=egcs@cygnus.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).