all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Omar Radwan <toxemicsquire4@gmail.com>
To: David Thompson <dthompson2@worcester.edu>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: wicd porting so far.
Date: Sat, 31 Jan 2015 19:04:52 -0800	[thread overview]
Message-ID: <CAMwaQALdC2b3-PTWdKN2MTJgarazBjRCsd-HE0bXAB5TWViN0g@mail.gmail.com> (raw)
In-Reply-To: <87zj8yjq1g.fsf@izanagi.i-did-not-set--mail-host-address--so-tickle-me>

[-- Attachment #1: Type: text/plain, Size: 883 bytes --]

>You need to run the './bootstrap' script first.  See the 'HACKING' file
>for more details about building from git.

after install autoconf as the hacking file suggested, the ./bootstrap now
complains about not having autopoint to run


On Sat, Jan 31, 2015 at 6:58 PM, David Thompson <dthompson2@worcester.edu>
wrote:

> Omar Radwan <toxemicsquire4@gmail.com> writes:
>
> >>Then make && ./pre-inst-env guix build wicd
> >
> > For starters, the make command returns an error
> > "make: *** No targets specified and no makefile found. Stop."
> >
> > Though there clearly are 2 makefiles. Makefile.in and Makefile.am
>
> You need to run the './bootstrap' script first.  See the 'HACKING' file
> for more details about building from git.
>
> --
> David Thompson
> Web Developer - Free Software Foundation - http://fsf.org
> GPG Key: 0FF1D807
> Support the FSF: https://fsf.org/donate
>

[-- Attachment #2: Type: text/html, Size: 1721 bytes --]

  reply	other threads:[~2015-02-01  3:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-31 19:21 wicd porting so far Omar Radwan
2015-01-31 19:27 ` Cyril Roelandt
2015-02-01  2:19   ` Omar Radwan
2015-02-01  2:58     ` David Thompson
2015-02-01  3:04       ` Omar Radwan [this message]
2015-02-01  3:08         ` David Thompson
2015-02-01 20:25           ` Omar Radwan
2015-02-02 14:16             ` 宋文武

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=CAMwaQALdC2b3-PTWdKN2MTJgarazBjRCsd-HE0bXAB5TWViN0g@mail.gmail.com \
    --to=toxemicsquire4@gmail.com \
    --cc=dthompson2@worcester.edu \
    --cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.