From: Justin moore <silve...@gmail.com>
To: voidlinux@googlegroups.com
Subject: pianobar fails to build without a build function
Date: Mon, 2 Feb 2015 01:45:30 -0800 (PST) [thread overview]
Message-ID: <7b43a249-f643-4ee2-9b39-bef3130c1220@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 446 bytes --]
I type 'make' and pianobar builds fine, however using a template and using
the build style gnu-makefile, the build fails. I looked at
/common/build_style/gnu-makefile.sh and everything looks fine. With the
arguments the style has, pianobar should be building fine (unless I am
missing something). If anyone would be willing to help me out and read over
my template file, that would be awesome
http://pastebin.com/4E3kkfi1
Thanks
[-- Attachment #1.2: Type: text/html, Size: 467 bytes --]
next reply other threads:[~2015-02-02 9:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-02 9:45 Justin moore [this message]
2015-02-02 12:47 ` Stefan Mühlinghaus
2015-02-02 23:50 ` Justin moore
2015-02-03 10:20 ` Juan RP
2015-02-04 7:45 ` Justin moore
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=7b43a249-f643-4ee2-9b39-bef3130c1220@googlegroups.com \
--to="silve..."@gmail.com \
--cc=voidlinux@googlegroups.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 NNTP newsgroup(s).