public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sylvain <asm8@wanadoo.fr>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] autoconf build error
Date: Sat, 3 May 2003 14:49:55 +0200	[thread overview]
Message-ID: <20030503144955.4a7c692d.asm8@wanadoo.fr> (raw)
In-Reply-To: <200305032106.40952.markc@renta.net>

Just for information, i had this problem also, and re-type the command (emerge system,
i think) and then no problem. I suppose you did it :-)

Le Sat, 3 May 2003 21:06:40 +1000
Mark Constable <markc@renta.net> a écrit:

> Apologies if this is not the right place to report this.
> This is going from a stage1 download onto a stage2 build
> for an athlon-tbird 1200.
> 
> >>> md5 ;-) autoconf-2.13.tar.gz
> >>> Unpacking source...
> >>> Unpacking autoconf-2.57.tar.bz2 to /var/tmp/portage/autoconf-2.57-r1/work
> >>> Unpacking autoconf-2.13.tar.gz to /var/tmp/portage/autoconf-2.57-r1/work
>  * Applying autoconf-2.13-configure-gentoo.diff...      [ ok ]
>  * Applying autoconf-2.13-configure.in-gentoo.diff...   [ ok ]
>  * Applying autoconf-2.57-infopage-namechange.patch...  [ ok ]
> >>> Source unpacked.
> checking for a BSD-compatible install... /bin/install -c
> checking whether build environment is sane... yes
> checking for gawk... gawk
> checking whether make sets $(MAKE)... yes
> checking for expr... /usr/bin/expr
> checking for gm4... no
> checking for gnum4... no
> checking for m4... no
> checking whether m4 supports frozen files... no
> configure: error: GNU M4 1.4 is required
> 
> !!! ERROR: sys-devel/autoconf-2.57-r1 failed.
> !!! Function src_compile, Line 50, Exitcode 1
> !!! (no error message)
> 
> --markc
> 
> 
> --
> gentoo-dev@gentoo.org mailing list
> 

--
gentoo-dev@gentoo.org mailing list


      parent reply	other threads:[~2003-05-03 12:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-03 11:06 [gentoo-dev] autoconf build error Mark Constable
2003-05-03 11:15 ` Paul de Vrieze
2003-05-03 12:49 ` Sylvain [this message]

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=20030503144955.4a7c692d.asm8@wanadoo.fr \
    --to=asm8@wanadoo.fr \
    --cc=gentoo-dev@gentoo.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