public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64]  Re: coreutils-6.4 - cannot compile
Date: Tue, 7 Nov 2006 08:39:25 +0000 (UTC)	[thread overview]
Message-ID: <eipgns$d05$1@sea.gmane.org> (raw)
In-Reply-To: 200611062236.11240.mmaroni@fi.uba.ar

Mauro Maroni <mmaroni@fi.uba.ar> posted
200611062236.11240.mmaroni@fi.uba.ar, excerpted below, on  Mon, 06 Nov
2006 22:36:11 -0300:

> References: <454F6945.1090704@ercbroadband.org>

> Did anyone get a segmentation fault when installing coreutils-6.4? See
> build error below

See that references header I quoted above?  That means you replied to a
previous post (which was on a totally different topic, gnupg, as it
happens), instead of starting a new thread. That's called hijacking a
thread, and is considered a violation of netiquette, as many people's
clients actually display threaded replies under the original post. If you
are replying, reply on topic. If you are starting a new topic, please do
it with a new post to a new thread, not a reply to an existing thread.

Briefly answering your question anyway... I have it merged here, which
means it must have merged just fine.  According to the date on one of the
package files, I merged it Oct. 24th.

I'm not an i18n/l10n (internationalization/localization) expert by far, as
I do only English and thus turn most of that stuff off where I can. 
However, if I'm not mistaken, po files are l10n related.  A quick google
says the .ar in your email address is Argentina, so it's relatively likely
you are localized to something other than the en-us I use and that tends
to be the default unlocalized version.  I'd do a bugsearch on
bugs.gentoo.org (don't forget to search on closed bugs too as it may have
just been fixed), and if there's nothing filed on the package that looks
like what you are seeing, file a bug report.  

In the mean time, you /might/ be able to merge it USE=-nls if you don't
mind giving up the l10n stuff. That is how I have it merged and would be
my guess as to what controls the po file stuff.

Still, that bug report is worthwhile, as the segfault points to an issue
that needs resolved.  (Be glad you aren't Estonian, "et" IIRC.  From a few
bug reports I've read, that l10n is one of the worst, as the letters are
in a different order resulting in all sorts of unanticipated stuff
happening when the normal ordering assumptions prove incorrect.  There's
an Estonian guy that has unfortunately had to become quite familiar with
bugzilla due to all the bugs he files as a result, but the devs appreciate
it as it points out bugs due to invalid assumptions, that nobody else
runs into.)

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@gentoo.org mailing list



  reply	other threads:[~2006-11-07  8:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-06 16:56 [gentoo-amd64] Gnupg doesn't build Mark Haney
2006-11-06 16:55 ` Daniel Gryniewicz
2006-11-06 18:00 ` Christoph Mende
2006-11-06 17:06   ` Mark Haney
2006-11-06 17:24     ` Neil Bothwick
2006-11-07  1:31 ` [gentoo-amd64] coreutils-6.4 - cannot install Mauro Maroni
2006-11-07  1:36 ` [gentoo-amd64] coreutils-6.4 - cannot compile Mauro Maroni
2006-11-07  8:39   ` Duncan [this message]
2006-11-08 23:25     ` [gentoo-amd64] " Mauro Maroni
2006-11-09 10:51       ` Duncan
2006-11-11 20:54         ` Mauro Maroni

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='eipgns$d05$1@sea.gmane.org' \
    --to=1i5t5.duncan@cox.net \
    --cc=gentoo-amd64@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox