From: Omar Radwan <toxemicsquire4@gmail.com>
To: Cyril Roelandt <tipecaml@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: wicd porting so far.
Date: Sat, 31 Jan 2015 18:19:19 -0800 [thread overview]
Message-ID: <CAMwaQAJH3TsswLt-FynfOH=TmSz3KdNhT4p0WMR3SUhLdTumjg@mail.gmail.com> (raw)
In-Reply-To: <54CD2CA4.1080608@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1097 bytes --]
>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
On Sat, Jan 31, 2015 at 11:27 AM, Cyril Roelandt <tipecaml@gmail.com> wrote:
> Hey,
>
> On 01/31/2015 08:21 PM, Omar Radwan wrote:
> > To begin with, I haven't gotten very far.
> >
> > I'm reading through the manual, and the first thing I figured out what to
> > do is write the package definition, http://pastebin.com/2q7LCv2i .
> >
> > I'm not sure what exactly to do with it, it was something about putting
> it
> > in the guix build tree. Though I'm not 100% sure what that is.
> >
>
> Clone the git repository:
>
> git clone git://git.savannah.gnu.org/guix.git
>
> Then cd guix and copy your recipe in gnu/packages/wicd.scm.
>
> Then make && ./pre-inst-env guix build wicd
>
> There will likely be a bunch of errors that you will have to figure out
> how to fix :) Do not hesitate to ask for help either on this
> mailing-list or on #guix on Freenode.
>
>
> Cyril.
>
[-- Attachment #2: Type: text/html, Size: 1921 bytes --]
next prev parent reply other threads:[~2015-02-01 2:19 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 [this message]
2015-02-01 2:58 ` David Thompson
2015-02-01 3:04 ` Omar Radwan
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='CAMwaQAJH3TsswLt-FynfOH=TmSz3KdNhT4p0WMR3SUhLdTumjg@mail.gmail.com' \
--to=toxemicsquire4@gmail.com \
--cc=guix-devel@gnu.org \
--cc=tipecaml@gmail.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.
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.