Displaying 20 results from an estimated 155 matches for "include_next".
2010 Jul 21
0
Samba install on AIX
...e.h-t warn-on-use.h && sed -n -e '/^.ifndef/,$p'
< ../build-aux/warn-on-use.h > warn-on-use.h-t && mv warn-on-use.h-t
warn-on-use.h
rm -f fcntl.h-t fcntl.h && { echo '/* DO NOT EDIT! GENERATED
AUTOMATICALLY! */'; sed -e 's|@''INCLUDE_NEXT''@|include_next|g' -e
's|@''PRAGMA_SYSTEM_HEADER''@|#pragma GCC system_header|g' -e
's|@''NEXT_FCNTL_H''@|<fcntl.h>|g' -e 's|@''GNULIB_FCNTL''@|1|g' -e
's|@''GNULIB_OPEN''@|1|g'...
2019 Aug 07
1
#include_next <stdio.h> not found
...l/clang7/bin/clang -I"/Library/Frameworks/R.framework/Resources/include" -DNDEBUG -I/usr/local/clang7/include/c++/v1 -fPIC -Wall -g -O2 -c mcmb.c -o mcmb.o
In file included from mcmb.c:11:
/usr/local/clang7/include/c++/v1/stdio.h:108:15: fatal error: 'stdio.h' file not found
#include_next <stdio.h>
^~~~~~~~~
My first thought was I should install Simon?s clang-7.0.0 and gfortran-6.1 packages
which I dutifully did. The next thought was to update my ~/.R/Makevars file to:
CC=/usr/local/clang7/bin/clang
CXX=/usr/local/clang7/bin/clang++
LDFLAGS=-L/usr/local/clang7...
2019 Aug 07
0
#include_next <stdio.h> not found
...l/clang7/bin/clang -I"/Library/Frameworks/R.framework/Resources/include" -DNDEBUG -I/usr/local/clang7/include/c++/v1 -fPIC -Wall -g -O2 -c mcmb.c -o mcmb.o
In file included from mcmb.c:11:
/usr/local/clang7/include/c++/v1/stdio.h:108:15: fatal error: 'stdio.h' file not found
#include_next <stdio.h>
^~~~~~~~~
My first thought was I should install Simon?s clang-7.0.0 and gfortran-6.1 packages
which I dutifully did. The next thought was to update my ~/.R/Makevars file to:
CC=/usr/local/clang7/bin/clang
CXX=/usr/local/clang7/bin/clang++
LDFLAGS=-L/usr/local/clang7...
2008 Aug 08
5
[LLVMdev] llvm-gcc builds on 32 bit linux broken
...building r54494 on 64bit linux and had the same (no
> include path)
> error. Any idea what's happening here?
>
No. :-( Could you try Mike's suggestion? (Replicated here)
Try adding:
#define _GCC_LIMITS_H_
to limitx.h like so:
#ifdef _GCC_NEXT_LIMITS_H
+#define _GCC_LIMITS_H_
#include_next <limits.h>
#undef _GCC_NEXT_LIMITS_H
and then testing. A good test would do a -dM -E and seeing if
everything is still defined and checking the testcase mentioned in the
original email thread.
2008 Jul 31
0
[LLVMdev] llvm-gcc builds on 32 bit linux broken
I think this error is due to these changes:
Doing diffs in .:
--- ./gsyslimits.h.~1~ 2006-11-26 12:31:50.000000000 -0800
+++ ./gsyslimits.h 2007-04-02 12:37:38.000000000 -0700
@@ -4,5 +4,3 @@
instead of this text. */
#define _GCC_NEXT_LIMITS_H /* tell gcc's limits.h to recurse */
-#include_next <limits.h>
-#undef _GCC_NEXT_LIMITS_H
--- ./limitx.h.~1~ 2006-11-26 12:31:48.000000000 -0800
+++ ./limitx.h 2007-04-02 13:51:40.000000000 -0700
@@ -1,12 +1,11 @@
/* This administrivia gets added to the beginning of limits.h
if the system has its own version of limits.h. */
-/* We use...
2011 Aug 03
1
[LLVMdev] dwarf directory table and file table
...ual header
> search path used.
>
> There are few wrinkles here, because these are preprocessor tokens.
>
Sure, but I was thinking of nabbing the actual string after macro expansion.
Clang's PresumedLoc.getIncludedLoc() points to the post-macro expansion
buffer.
> - What about #include_next ?
> - #include <Foo/Foo.h> does not mean {include path ...}/Foo/Foo.h for
> Apple's framework header.
> - Some IDEs, like Xcode, uses header maps. If you're curious search
> HeaderMaps in clang FE.
>
> The dwarf line table should be able to encode directory names. I...
2008 Jul 30
3
[LLVMdev] llvm-gcc builds on 32 bit linux broken
Hi all,
I'm having some trouble building llvm-gcc as of today, with and without
bootstrap.
The error I get is:
/home/kooijman/src/llvm-gcc/obj/./gcc/xgcc
-B/home/kooijman/src/llvm-gcc/obj/./gcc/
-B/home/kooijman/src/llvm-gcc/obj/../install/i686-pc-linux-gnu/bin/
-B/home/kooijman/src/llvm-gcc/obj/../install/i686-pc-linux-gnu/lib/ -isystem
2020 Aug 18
1
Re: [PATCH nbdkit 3/9] server: Add general replacements for missing functions using LIBOBJS.
...if /* NBDKIT_STRNDUP_H */
> diff --git a/common/replacements/syslog.h b/common/replacements/syslog.h
> new file mode 100644
> index 00000000..e4d76677
> --- /dev/null
> +++ b/common/replacements/syslog.h
> +#include <config.h>
> +
> +#ifdef HAVE_SYSLOG_H
> +
> +#include_next <syslog.h>
I guess our insistence on a decent compiler (for other reasons such as
__attribute__((cleanup))) means we can rely on #include_next ;)
> +++ b/common/replacements/getdelim.c
> @@ -0,0 +1,84 @@
> +/* $NetBSD: getdelim.c,v 1.2 2015/12/25 20:12:46 joerg Exp $ */
> +/* N...
2011 Aug 03
0
[LLVMdev] dwarf directory table and file table
...lly want for a file is to enter the actual name of the header that the preprocessor found between "" or <> on the #include line, and for the directory it should be the actual header search path used.
There are few wrinkles here, because these are preprocessor tokens.
- What about #include_next ?
- #include <Foo/Foo.h> does not mean {include path ...}/Foo/Foo.h for Apple's framework header.
- Some IDEs, like Xcode, uses header maps. If you're curious search HeaderMaps in clang FE.
The dwarf line table should be able to encode directory names. I am not sure, what is the adv...
2017 Jun 12
0
AIX lacks getopt_long
...es.
michael at x071:[/data/prj/aixtools/github/dovecot/src/x071-test]/data/prj/aixtools/github/dovecot/gnulib/gnulib-tool
--dry-run --import getopt-posix
Module list with included dependencies (indented):
absolute-header
extensions
extern-inline
getopt-posix
gettext-h
include_next
snippet/arg-nonnull
snippet/c++defs
snippet/warn-on-use
ssize_t
stddef
sys_types
unistd
File list:
lib/arg-nonnull.h
lib/c++defs.h
lib/getopt-cdefs.in.h
lib/getopt-core.h
lib/getopt-ext.h
lib/getopt-pfx-core.h
lib/getopt-pfx-ext.h
lib/getop...
2011 Aug 03
3
[LLVMdev] dwarf directory table and file table
I've been looking into the debug info in llvm recently. After conferring
with a DWARF expert, I think what we really want for a file is to enter the
actual name of the header that the preprocessor found between "" or <> on
the #include line, and for the directory it should be the actual header
search path used.
I started by taking a look at how LLVM encodes this in a .s file
2008 Aug 08
0
[LLVMdev] llvm-gcc builds on 32 bit linux broken
> to limitx.h like so:
>
> #ifdef _GCC_NEXT_LIMITS_H
> +#define _GCC_LIMITS_H_
> #include_next <limits.h>
> #undef _GCC_NEXT_LIMITS_H
This fixes this problem for me on Ubuntu Hardy on x86-64.
John
2010 Mar 17
1
Where to find Intrinsic.h and xlib.h
...search for these two file by 'locate'. Only find them:
/usr/include/xulrunner-sdk-1.9/system_wrappers/X11/Intrinsic.h
/usr/include/xulrunner-sdk-1.9/system_wrappers/X11/Xlib.h
And there are nothingin these two files. :
Xlib.h?
#pragma GCC system_header
#pragma GCC visibility push(default)
#include_next <X11/Xlib.h>
#pragma GCC visibility pop
Intrinsic.h
#pragma GCC system_header
#pragma GCC visibility push(default)
#include_next <X11/Intrinsic.h>
#pragma GCC visibility pop
Them I install libX11-devel and reinstall xorg-x11-proto-devel. But still
can't find Xlib.h and Intrinsic.h...
2008 Aug 08
0
[LLVMdev] llvm-gcc builds on 32 bit linux broken
...nclude path)
>> error. Any idea what's happening here?
>>
> No. :-( Could you try Mike's suggestion? (Replicated here)
>
> Try adding:
>
> #define _GCC_LIMITS_H_
>
> to limitx.h like so:
>
> #ifdef _GCC_NEXT_LIMITS_H
> +#define _GCC_LIMITS_H_
> #include_next <limits.h>
> #undef _GCC_NEXT_LIMITS_H
>
> and then testing. A good test would do a -dM -E and seeing if
> everything is still defined and checking the testcase mentioned in the
> original email thread.
> _______________________________________________
> LLVM Developers...
2020 Aug 17
2
How to run the test suite on macOS?
...om /Users/stephan/Software/llvm/build/./bin/../include/c++/v1/ios:214:
> In file included from /Users/stephan/Software/llvm/build/./bin/../include/c++/v1/iosfwd:95:
> /Users/stephan/Software/llvm/build/./bin/../include/c++/v1/wchar.h:119:15: fatal error: 'wchar.h' file not found
> #include_next <wchar.h>
> ^~~~~~~~~
> 1 error generated.
Am I missing anything like setting up an appropriate environment, or
passing appropriate values for some cmake -D configuration switches?
2019 Aug 03
3
conflicting builtins in clang with musl (stddef.h)
...e/stddef.h.
# clang++ -std=c++17 -isystem /include test.cpp
In file included from test.cpp:2:
In file included from /bin/../include/c++/v1/limits:106:
In file included from /bin/../include/c++/v1/type_traits:406:
/bin/../include/c++/v1/cstddef:45:15: fatal error: 'stddef.h' file not
found
#include_next <stddef.h>
^~~~~~~~~~
1 error generated.
I'm scratching my hair trying to understand what is wrong and what
should I do here.
Also, I can't understand why CMake adds all these -isystem include
directories. But this is a webkit issue I guess.
Any ideas/recommandations...
2011 Jun 07
3
builder-debian febootstrap success d6d144eab55388d4117880f2d3a7e8c2571c9d9a
...double-slash-root
dup2
errno
error
exitfail
extensions
fchdir
fclose
fcntl
fcntl-h
fcntl-safer
fdopendir
filevercmp
float
fts
full-write
getcwd
getdtablesize
getopt-gnu
getopt-posix
gettext-h
hash
hash-pjw
i-ring
include_next
inline
intprops
inttypes
lchown
lstat
malloc-posix
memchr
mempcpy
memrchr
mkdir
multiarch
open
openat
openat-die
openat-safer
realloc-posix
rmdir
safe-read
safe-write
same-inode
save-cwd
size_max
ssize_t...
2008 Aug 07
2
[LLVMdev] llvm-gcc builds on 32 bit linux broken
Hi Matthijs,
>> I did put in a hack, but it was horrible. It might be a good idea to
>> test out Mike's suggestion to see if it's a better way of doing it.
> I just tried building llvm-gcc without your hack, and it still works (even
> without the fix Mike suggested).
>
> So, it seems that r54245 can be reverted again?
>
> I didn't test bootstrap, however,
2008 Aug 08
0
[LLVMdev] llvm-gcc builds on 32 bit linux broken
I've just tried building r54494 on 64bit linux and had the same (no
include path)
error. Any idea what's happening here?
Thanks,
-David Shipman
On Fri, Aug 8, 2008 at 6:12 AM, Bill Wendling <isanbard at gmail.com> wrote:
> Hi Matthijs,
>
>>> I did put in a hack, but it was horrible. It might be a good idea to
>>> test out Mike's suggestion to see if
2008 Sep 07
2
xulrunner-devel package missing many header files
...ulrunner-sdk-1.9/sdk/include:
mozilla-config.h
mozilla-config32.h
prtypes.h
The include/xulrunner-sdk-1.9 constains those above header files, I
did link to them, but xulrunner-sdk-1.9/system_wrappers/prtypes.h has
a problem as well:
#pragma GCC system_header
#pragma GCC visibility push(default)
#include_next <prtypes.h>
#pragma GCC visibility pop
At final, I could not compile VLC plugin with the
xulrunner-sdk-1.9/sdk. Please advice how to fix it and where could I
install a proper sdk?
Thank you.
Kind regards,
Jim