Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sergey Gusarov <laborer2008@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Note on the large files support in sqlite(as part of Qt)
Date: Thu, 07 Jul 2011 15:38:55 +0400	[thread overview]
Message-ID: <4E159ACF.7030508@gmail.com> (raw)
In-Reply-To: <87iprft86n.fsf@macbook.be.48ers.dk>

07.07.2011 01:23, Peter Korsgaard writes:

 >> Patch from qt bugtracker already included in the upstream, at least 
it is in the Qt 4.7.3 release.
 > Really?
 > $ grep -rls SQLITE_DISABLE_LFS qt-everywhere-opensource-src-4.7.3
 > qt-everywhere-opensource-src-4.7.3/src/3rdparty/sqlite/sqlite3.c
 > $

Oh, i was wrong. My Qt 4.7.3 sources were already patched. The patch is 
not yet included. Nevertheless, it seems correct errors in upsteam 
project more accurately.

 >Did you try it?
Yes. I compiled qt with uclibc-based toolchain without LFS. You also can 
try to do this.

Regards, Sergey

  reply	other threads:[~2011-07-07 11:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-06 19:47 [Buildroot] Note on the large files support in sqlite(as part of Qt) Sergey Gusarov
2011-07-06 21:23 ` Peter Korsgaard
2011-07-07 11:38   ` Sergey Gusarov [this message]
2011-07-07 11:46     ` Peter Korsgaard
2011-07-07 21:00       ` Sergey Gusarov

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=4E159ACF.7030508@gmail.com \
    --to=laborer2008@gmail.com \
    --cc=buildroot@busybox.net \
    /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