Displaying 9 results from an estimated 9 matches for "configlex".
Did you mean:
config_len
2004 Sep 01
0
[LLVMdev] FreeBSD Support In lib/System
...right now, so I'm forwarding my recent
> submissions to you directly.
>
> =============================================================
>
> My experiment to build as if Linux has failed:
>
> gmake[1]: Entering directory `/usr/home/llvm/obj/tools/llvmc'
> Compiling ConfigLexer.cpp
> /usr/home/llvm/obj/../tools/llvmc/ConfigLexer.l: In function `
> llvm::ConfigLexerTokens handleSubstitution(llvm::ConfigLexerTokens)':
> /usr/home/llvm/obj/../tools/llvmc/ConfigLexer.l:66: error: `assert' undeclared
> (first use this function)
> /usr/home/llvm/...
2004 Aug 31
9
[LLVMdev] POSIX compliance
Reid,
>As for Interix support in general, I'm having a hard time determining
>which variant of Unix Interix implements. It seems to be partially Posix
>1 and partially Posix 2 based. Do you have any further information
>related to the specific standards supported by Interix? I don't want to
>incorrectly categorize the Interix support.
I've discussed this subject with
2004 Aug 31
0
[LLVMdev] FreeBSD Support In lib/System
Jeff/Vladimir:
As with Interix, I've recently added support for FreeBSD into
lib/System. Currently, the implementation of FreeBSD just uses the
"generic Unix" implementation which probably should work on FreeBSD. If
not, I would appreciate it if you could make patches in the FreeBSD
directory. If you do, don't forget that you need to remove anything that
doesn't work in the
2012 Nov 28
1
Build error of NSD4 on Debian Squeeze
Hello World,
I am trying to build NSD4 on Debian Squeeze and I get the following
errors when running `make`.
```
$ pwd
/home/wiz/src/nsd/tags/NSD_4_0_0_imp_5
$ make
[... output omitted ...]
gcc -g -O2 -o nsd-checkconf answer.o axfr.o buffer.o configlexer.o
configparse
acket.o query.o rbtree.o radtree.o rdata.o region-allocator.o tsig.o
tsig-opens
4_pton.o b64_ntop.o -lcrypto
configparser.o: In function `c_parse':
/home/wiz/src/nsd/tags/NSD_4_0_0_imp_5/configparser.c:609: undefined
reference
/home/wiz/src/nsd/tags/NSD_4_0_0_imp_5/configparser....
2004 Sep 01
2
[LLVMdev] Problem with CVS LLVM build in obj != src dir case
...rectory `/usr/home/wanderer/pkg/build/llvm/obj/projects'
gmake: *** [all] Error 1
Some new warnings from last successful buld some days ago:
1) flex
gmake[2]: Entering directory
`/usr/home/wanderer/pkg/build/llvm/obj/tools/llvmc'
Flexing /home/wanderer/pkg/build/llvm/src/llvm/tools/llvmc/ConfigLexer.l
"/home/wanderer/pkg/build/llvm/src/llvm/tools/llvmc/ConfigLexer.l", line
191: warning, -s option given but default rule can be matched
gmake[2]: Leaving directory
`/usr/home/wanderer/pkg/build/llvm/obj/tools/llvmc'
2) gcc 3.5 (mainline CVS)
Mostly result using ~0 (signed int) e...
2004 Sep 02
0
[LLVMdev] Problem with CVS LLVM build in obj != src dir case
...wanderer/pkg/build/llvm/obj/projects'
gmake: *** [all] Error 1
> Also some new warnings from last successful buld some days ago:
>
> 1) flex
gmake[2]: Entering directory
`/usr/home/wanderer/pkg/build/llvm/obj/tools/llvmc'
Flexing /home/wanderer/pkg/build/llvm/src/llvm/tools/llvmc/ConfigLexer.l
"/home/wanderer/pkg/build/llvm/src/llvm/tools/llvmc/ConfigLexer.l", line
191: warning, -s option given but default rule can be matched
gmake[2]: Leaving directory
`/usr/home/wanderer/pkg/build/llvm/obj/tools/llvmc'
> 2) gcc 3.5 (mainline CVS)
> Mostly result using ~0 (neg...
2004 Sep 01
1
[LLVMdev] POSIX compliance
Thanks for noting it. I'll see what cygwin has to offer in this area and
correct the implementation.
Thanks,
Reid.
On Wed, 2004-09-01 at 09:11, Valery A.Khamenya wrote:
> /lib/System/platform/Path.cpp is not compilable under Cygwin
> (although it was motivated to be for Cygwin...):
> -----------------------------------
> Compiling Path.cpp
> In file included from
2004 Sep 02
1
[LLVMdev] Problem with CVS LLVM build in obj != src dir case
...igure in the build directory ?
>
> > Also some new warnings from last successful buld some days ago:
> >
> > 1) flex
> gmake[2]: Entering directory
> `/usr/home/wanderer/pkg/build/llvm/obj/tools/llvmc'
> Flexing /home/wanderer/pkg/build/llvm/src/llvm/tools/llvmc/ConfigLexer.l
> "/home/wanderer/pkg/build/llvm/src/llvm/tools/llvmc/ConfigLexer.l", line
> 191: warning, -s option given but default rule can be matched
> gmake[2]: Leaving directory
> `/usr/home/wanderer/pkg/build/llvm/obj/tools/llvmc'
That one's okay. If I could figure out...
2007 Jul 05
2
[LLVMdev] PATCH (rest of code changes) "bytecode" --> "bitcode"
Here is the bulk of the sanitizing.
My residual doubts center around the question
whether we still do/want to support (un)compressed *byte*code
in 2.0/2.1.
I need a definitive word on this to proceed.
My understanding is that bytecode is already gone, but there are
still some functions/enums that really deal with *byte*code
(instead of *bit*code).
I did not touch those areas, so the attached