mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] gettext libintl issues
Date: Tue, 5 Mar 2013 21:27:45 +0100	[thread overview]
Message-ID: <20130305202743.GA776@x61s.8.8.8.8> (raw)
In-Reply-To: <20130305111819.GB7949@pengutronix.de>

Hi,

On Tue, Mar 05, 2013 at 12:18:19PM +0100, Michael Olbrich wrote:
> Hi,
> 
> On Tue, Mar 05, 2013 at 11:35:48AM +0100, Alexander Aring wrote:
> > I have some trouble to port some software and getting a "undefined
> > reference to `textdomain(char const*)'" error.
> > 
> > The textdomain function is a part of libintl, so far as I know.
> > 
> > In file rules/gettext.in is a useless config entry for GETTEXT_LIBINTL.
> > After I grep GETTEXT_LIBINTL in all configs, this will never used by
> > any package.
> > 
> > A git log gives no more information about other important changes.
> > 
> > I will try to fix this issue.
> > Has anybody got the same issue. Or is this still on a TODO list?
> 
> All the gettext stuff is in a 'It works for me' state. I don't really know
> how this stuff is supposed to work. The only package that generates a
> libintl is gettext-dummy.
> 
> Where do you get the prototype for textdomain() anyways? That's usually a
> macro (I think).
>
I solved it. It's not a problem with gettext... some stupid mistake which
was fixed by rebuild of other libaries. :-)

Anyway I could send patches to remove GETTEXT_LIBINTL in rules/gettext.in
if you like that. This config is never used in other rules or will select
some other configs, ptxdist don't need this config.

Alex

-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2013-03-05 20:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-05 10:35 Alexander Aring
2013-03-05 11:18 ` Michael Olbrich
2013-03-05 20:27   ` Alexander Aring [this message]
2013-03-06  7:42     ` Michael Olbrich

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=20130305202743.GA776@x61s.8.8.8.8 \
    --to=alex.aring@gmail.com \
    --cc=ptxdist@pengutronix.de \
    /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