all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dmitry Bogatov <KAction@gnu.org>
To: Alex Vong <alexvong1995@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] NON-WORKING: new package: sent -- simple presentation tool
Date: Sun, 13 Dec 2015 19:47:52 +0300	[thread overview]
Message-ID: <20151213164742.GC7888@sagulo> (raw)
In-Reply-To: <CADrxHD84rOJABnvmhvSVUsYDEo2MCP=tips_o1GAXnMMoW4qEw@mail.gmail.com>

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

* Alex Vong <alexvong1995@gmail.com> [2015-12-14 00:07:53+0800]
> Hi,
> 
> I haven't really look into the source but perhaps the build log has
> answered your question :) (or not?)
> 
> In the build log, there are three suspicious lines:
> CFLAGS   = -g -std=c99 -pedantic -Wall -I. -I/usr/include
> -I/usr/include/freetype2 -I/usr/X11R6/include -DVERSION="0.2"
> -D_XOPEN_SOURCE=600
> LDFLAGS  = -g -L/usr/lib -lc -lm -L/usr/X11R6/lib -lXft -lfontconfig -lX11 -lpng
> CC       = gcc
> 
> It seems the paths are hard-coded (It is my guess), so it works in
> Debian only because of luck. I suppose if the libraries were installed
> into `/usr/local', which is permitted by the FHS, then the build
> system won't able to find it. I think the way to fix it is to add an
> additional phase to patch the build system.

I thought about it. But then why Xft headers are found, but freetype are
not? I believe, that guix provides CFLAGS enviroment, which overrides
config.mk

-- 
Accept: text/plain, text/x-diff
Accept-Language: eo,en,ru
X-Keep-In-CC: yes
X-Web-Site: sinsekvu.github.io

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-12-13 16:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-12 21:44 [PATCH] NON-WORKING: new package: sent -- simple presentation tool KAction
2015-12-13 16:07 ` Alex Vong
2015-12-13 16:47   ` Dmitry Bogatov [this message]
2015-12-13 18:48 ` Leo Famulari
2015-12-14 11:14   ` Alex Vong
2016-08-13  9:35     ` ng0
2016-08-14  6:52       ` Eric Bavier
2016-08-14  8:04         ` Dmitry Bogatov
2016-08-16 19:26           ` Eric Bavier

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=20151213164742.GC7888@sagulo \
    --to=kaction@gnu.org \
    --cc=alexvong1995@gmail.com \
    --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.