This applies to KDE4, where we are careful enough to avoid any off_ts in procfs structs. We need to build gnulib under some other directory not # "gnulib", to avoid the problem of both GDB and GDBserver wanting to # build it in the same directory, when This is the mail archive of the [email protected] mailing list for the GDB project. Reload to refresh your session. http://sonoportal.net/cannot-use/cannot-use-process-in-the-large-file-compilation-environment.html
This is sub-optimal for us, for example reading /proc entries for 64-bit processes doesn't work when collectd is 32-bit. These are documented inthe lfcompile(5) man page as off_t, rlim_t, ino_t, blkcnt_t, fsblkcnt_t,and fsfilcnt_t. Sign in to comment Contact GitHub API Training Shop Blog About © 2016 GitHub, Inc. This is what happens on Solaris when configure inappropriately defines _FILE_OFFSET_BITS as nothing: config.log: configure:47832: g++ -c -Wnon-virtual-dtor -Wno-long-long -Wundef -Wall -W -Wpointer-arith -Wwrite-strings -g3 -fno-inline -fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST https://sourceware.org/ml/gdb-patches/2014-12/msg00058.html
I was assuming it was 32bit, meaning that 64bit kernel / userland would not be able to run there. Can you try writing a dg-effective-target test? It doesn't seem to be working >How-To-Repeat: download gdb 6.3 stable export CFLAGS="-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64" go to the directory and type ./configure type make You should see the problem now. >Fix: >Release-Note: Already have an account?
Using > gdb-6.1 works fine. Authentication-results: sourceware.org; auth=none References: <20141203104812 dot GA14666 at adacore dot com> This patch mostly aims at fixing a GDB build failure on 32bit Solaris systems (Sparc and x86), due to a It doesn't seem to be working I don't think there's anything we can do with this - it comes from the Solaris system headers... collectd member octo commented Jun 11, 2015 FYI, it compiles now past the zone plugin but failes ultimately due to #978.
Over the years, many reasons have been offered up for this; they have ranged from the demonstrably false (e.g., asserting that the kernel cannot differentiate large file awareness in a 32-bit If not, couldn't this simple change be made?There should be no need for this - off_t itself can either be a32-bit or 64-bit value depending on the compilation mode, asyou can AFAIK, the kernel has noway of knowing that a 32-bit process was compiled with large filesupport, only that it's a 32-bit process vs a 64-bit process. https://groups.google.com/d/topic/comp.unix.solaris/0I3iFRJUmeQ Maybe the lto-plugin could perform some check with dlsym (for open64?)?
When large files is enabled the file access data structures are enhanced to use 64 bit again which is not possible when the /proc structures are 32 bit, hence the problem. But I think I got close enoughthat it makes sense if you think about it why procfs.h behaves the wayit does.I think the reason is really pretty simple: in the lfcompileenvironment, Rainer Comment 3 Rainer Orth 2011-11-21 16:41:54 UTC It took me a while, but the issue turned out to be different: * Toplevel config/largefile.m4 disables largefile support for 32-bit Solaris, and Comment 6 ro@CeBiTec.Uni-Bielefeld.DE 2011-11-21 17:30:21 UTC > --- Comment #5 from Paolo Bonzini
The previous AC_CHECK_HEADERS already contains #undef _FILE_OFFSET_BITS which prevents the check from failing … octo added a commit that referenced this issue Jun 11, 2015 octoThis is done by first enhancing ACX_CONFIGURE_DIR to allow us to pass extra arguments to be passed to the configure command, and then by modifying GDB's configure to pass --disable-largefile if dago commented Jun 11, 2015 It will work partly ok as 32 bit processes can not stat 64 bit processes, so this will most certainly return inaccurate results. no configure: Solaris detected.
diff --git a/usr/src/uts/common/fs/proc/prvnops.c b/usr/src/uts/common/fs/proc/p index a3e95a6..7831c1f 100644 --- a/usr/src/uts/common/fs/proc/prvnops.c +++ b/usr/src/uts/common/fs/proc/prvnops.c @@ -23,6 +23,10 @@ * Copyright (c) 1989, 2010, Oracle and/or its affiliates. http://sonoportal.net/cannot-use/cannot-use-procfs-in-the.html collectd member octo commented Jun 11, 2015 Thanks for the explanation @dago, it makes sense now! You signed out in another tab or window. So don't. ;-}--James Carlson 42.703N 71.076W
Does that about sum it up? So unless the user explicitly requested # large-file support through the --enable-largefile switch, disable # large-file support in favor of procfs support. A side-effect of the gnulib readlink module addition is that it caused largefile support to be added as well, and in particular gnulib/import/m4/largefile.m4 introduced the following new #define in gnulib's config.in: navigate here However, without -m64 the compiler generates 32 bit code which can also run on a 64 bit kernel.
When I >> try >> > to compile the "start-stop-daemon" >> > program, "configure" goes fine: >> > >> > # ./configure --prefix=/usr/local/gw >> --enable-start-stop-daemon >> > >> > However, "make" Powered by Redmine © 2006-2015 Jean-Philippe Lang OSDir.com gdb.bugs.discuss Subject: build/2006: "Cannot use procfs in large filecompilation environment" Date Index Thread: Prev Next Thread Index >Number: 2006 >Category: build gdb (and only gdb AFAIK) uses procfs, and Solaris procfs doesn't support a largefile environment, no idea why?
I can't reproduce this. But it might also fix related issues when configuring with --disable-largefile. Comment 3 Steve Evans 2004-10-14 17:38:30 UTC On 12 Oct 2004, email@example.com wrote: > ------- You are receiving this mail because: ------- > You reported the bug, or are watching the his comment is here checking for ANSI C header files... (cached) yes The problem seems to be that neither CFLAGS nor LDFLAGS is used during this test and hence -m64 is not set at all:
Terms Privacy Security Status Help You can't perform that action at this time. Also available in: Atom Loading... Rainer Comment 4 ro@CeBiTec.Uni-Bielefeld.DE 2011-11-21 16:50:54 UTC I forgot: while one could use ACX_LARGEFILE everywhere in GCC (and I tried that using --disable-largefile when configuring gcc works with a default-configured gld), Reload to refresh your session.
We can't use AC_CONFIG_SUBDIRS as that'd expect # to find the the source subdir to be configured directly under # gdbserver/. Alternatiely, one could simply document the problem in install.texi and be done with it. Status:ResolvedStart date:2012-03-15Priority:NormalDue date:Assignee:Bryan Cantrill% Done:100%Category:kernelTarget version:- Difficulty:Bite-size Tags: Description When attempting to include
© Copyright 2017 sonoportal.net. All rights reserved.