Mercurial > hg > xemacs-beta
view etc/toolbar/info-def-up.xpm @ 5727:86d33ddc7fd6
Avoid EOVERFLOW from stat() calls due to overflowing inode numbers.
The btrfs filesystem now uses 64-bit inode numbers even on 32-bit systems.
This can lead to spurious stat() failures, where EOVERFLOW is returned because
the inode number does not fit into the 32-bit stat structure, even when the
caller is not interested in the inode number. This patch builds with
_FILE_OFFSET_BITS == 64 when possible, and deals with integers that may be
too large to fit into a Lisp fixnum. For more information, see xemacs-patches
message <CAHCOHQk_mPM6WgFChBsGafqhuazep6VED7swFoqfFXOV1r8org@mail.gmail.com>.
| author | Jerry James <james@xemacs.org> |
|---|---|
| date | Wed, 06 Mar 2013 08:32:17 -0700 |
| parents | 7910031dd78a |
| children |
line wrap: on
line source
/* XPM */ /* This file is part of XEmacs. XEmacs is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. XEmacs is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with XEmacs. If not, see <http://www.gnu.org/licenses/>. */ static char * info[] = { "28 28 2 1", "X c Gray75 s backgroundToolBarColor", "o c black s foregroundToolBarColor", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXoXXXXXXXXXXXXXX", "XXXXXXXXXXXoooooXXXXXXXXXXXX", "XXXXXXXXXXXoooooXXXXXXXXXXXX", "XXXXXXXXXXoooooooXXXXXXXXXXX", "XXXXXXXXXXXoooooXXXXXXXXXXXX", "XXXXXXXXXXXoooooXXXXXXXXXXXX", "XXXXXXXXXXXXXoXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXooooooXXXXXXXXXXXX", "XXXXXXXXXoooooooXXXXXXXXXXXX", "XXXXXXXXXXXoooooXXXXXXXXXXXX", "XXXXXXXXXXXoooooXXXXXXXXXXXX", "XXXXXXXXXXXoooooXXXXXXXXXXXX", "XXXXXXXXXXXoooooXXXXXXXXXXXX", "XXXXXXXXXXXoooooXXXXXXXXXXXX", "XXXXXXXXXXXoooooXXXXXXXXXXXX", "XXXXXXXXXXXoooooXXXXXXXXXXXX", "XXXXXXXXXXXoooooXXXXXXXXXXXX", "XXXXXXXXXXXoooooXXXXXXXXXXXX", "XXXXXXXXXXoooooooXXXXXXXXXXX", "XXXXXXXXXoooooooooXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX"};