All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ismail Dönmez" <ismail@pardus.org.tr>
To: Jan Hudec <bulb@ucw.cz>
Cc: Marco Costalba <mcostalba@gmail.com>,
	Git Mailing List <git@vger.kernel.org>,
	Pavel Roskin <proski@gnu.org>,
	Andy Parkins <andyparkins@gmail.com>
Subject: Re: [ANNOUNCE] qgit-2.0rc1
Date: Sun, 10 Jun 2007 21:10:04 +0300	[thread overview]
Message-ID: <200706102110.14258.ismail@pardus.org.tr> (raw)
In-Reply-To: <20070610175628.GI4084@efreet.light.src>

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

On Sunday 10 June 2007 20:56:28 Jan Hudec wrote:
> On Sun, Jun 10, 2007 at 19:33:31 +0300, Ismail Dönmez wrote:
> > On Sunday 10 June 2007 17:36:42 you wrote:
> > > On 6/10/07, Ismail Dönmez <ismail@pardus.org.tr> wrote:
> > > > Uploaded to
> > > > http://cekirdek.pardus.org.tr/~ismail/tmp/qgit4-report.txt .
> > >
> > > Ok. You seem to miss all the debug libraries  _and_ the whole
> > > libQtUiTools library.
> >
> > Nope not a Qt problem. Removing -frepo from CXXFLAGS fixes the issue. Gcc
> > 4.2.0 doesn't seem to like it for some reason.
>
> I did a brief STFW and found problems with -frepo to be rather common. From
> what I understood, it works by trying to link, parsing the errors,
> instantiating the missing bits and compiling again. And the whole thing is
> rather fragile.
>
> What could be interesting for you is debian bug
> http://lists.debian.org/debian-gcc/2007/05/msg00374.html
>
> It says that -frepo only works with C locale, but it would actually be in
> any locale where ld messages are not localized. On my system it has message
> catalog in da, es, fr, ga, sv, tr, vi, zh_CN and zh_TW. Don't you have
> tr_TR for LC_MESSAGES?

My LC_ALL is tr_TR.UTF-8. Btw LC_ALL=C make gives the same problem.

Regards,
ismail

-- 
Perfect is the enemy of good

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 827 bytes --]

  reply	other threads:[~2007-06-10 18:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-10 11:47 [ANNOUNCE] qgit-2.0rc1 Marco Costalba
2007-06-10 12:14 ` Ismail Dönmez
     [not found]   ` <e5bfff550706100529xaeac76erc1dff124c1fac470@mail.gmail.com>
2007-06-10 12:40     ` Ismail Dönmez
     [not found]       ` <e5bfff550706100549y199dcce6o2989744ff55ac8d7@mail.gmail.com>
2007-06-10 12:56         ` Ismail Dönmez
     [not found]           ` <e5bfff550706100626t2d5721a6r7beb0cfeb19dff4@mail.gmail.com>
2007-06-10 13:40             ` Marco Costalba
2007-06-10 13:45               ` Ismail Dönmez
     [not found]                 ` <e5bfff550706100659l41c392f4n9dc9fb3097f3da29@mail.gmail.com>
2007-06-10 14:04                   ` Ismail Dönmez
     [not found]                     ` <e5bfff550706100736v110055acn8ecca19f5c3f5cff@mail.gmail.com>
2007-06-10 14:49                       ` Ismail Dönmez
2007-06-10 16:33                       ` Ismail Dönmez
2007-06-10 17:56                         ` Jan Hudec
2007-06-10 18:10                           ` Ismail Dönmez [this message]
2007-06-10 21:36                           ` Marco Costalba
2007-06-10 13:41             ` Ismail Dönmez
2007-06-10 14:03 ` Jan Hudec
2007-06-10 14:21   ` Marco Costalba

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=200706102110.14258.ismail@pardus.org.tr \
    --to=ismail@pardus.org.tr \
    --cc=andyparkins@gmail.com \
    --cc=bulb@ucw.cz \
    --cc=git@vger.kernel.org \
    --cc=mcostalba@gmail.com \
    --cc=proski@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.
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.