search for: _parse_file

Displaying 8 results from an estimated 8 matches for "_parse_file".

Did you mean: parse_file
2009 Sep 25
6
[LLVMdev] JIT on ARM
...llvm-gcc4.2-objects/ gcc/../../llvm-gcc4.2-2.4.source/gcc/gengtype.c:725: more undefined references to `_lexer_line' follow build/gengtype.o: In function `main': /cygdrive/r/android/llvm/llvm-gcc4.2-objects/gcc/../../llvm- gcc4.2-2.4.source/gcc/gengtype.c:3070: undefined reference to `_parse_file' /cygdrive/r/android/llvm/llvm-gcc4.2-objects/gcc/../../llvm- gcc4.2-2.4.source/gcc/gengtype.c:3070: undefined reference to `_parse_file' build/gengtype-yacc.o: In function `yyparse': /cygdrive/r/android/llvm/llvm-gcc4.2-objects/gcc/../../llvm- gcc4.2-2.4.source/gcc/gengtype-yacc.y:...
2009 Oct 14
0
[LLVMdev] JIT on ARM
...; gcc/../../llvm-gcc4.2-2.4.source/gcc/gengtype.c:725: more undefined > references to `_lexer_line' follow > build/gengtype.o: In function `main': > /cygdrive/r/android/llvm/llvm-gcc4.2-objects/gcc/../../llvm- > gcc4.2-2.4.source/gcc/gengtype.c:3070: undefined reference to > `_parse_file' > /cygdrive/r/android/llvm/llvm-gcc4.2-objects/gcc/../../llvm- > gcc4.2-2.4.source/gcc/gengtype.c:3070: undefined reference to > `_parse_file' > build/gengtype-yacc.o: In function `yyparse': > /cygdrive/r/android/llvm/llvm-gcc4.2-objects/gcc/../../llvm- > gcc4.2-2.4.s...
2009 Oct 14
0
[LLVMdev] Fwd: JIT on ARM
.../../../llvm-gcc4.2-2.4.source/gcc/gengtype.c:725: more undefined > references to `_lexer_line' follow > build/gengtype.o: In function `main': > /cygdrive/r/android/llvm/llvm-gcc4.2-objects/gcc/../../llvm- > gcc4.2-2.4.source/gcc/gengtype.c:3070: undefined reference to > `_parse_file' > /cygdrive/r/android/llvm/llvm-gcc4.2-objects/gcc/../../llvm- > gcc4.2-2.4.source/gcc/gengtype.c:3070: undefined reference to > `_parse_file' > build/gengtype-yacc.o: In function `yyparse': > /cygdrive/r/android/llvm/llvm-gcc4.2-objects/gcc/../../llvm- > gcc4.2-2...
2017 Jun 19
16
[PATCH v7 00/13] Refactor utilities
This is just the utilities part of the patch series from: https://www.redhat.com/archives/libguestfs/2017-June/msg00103.html I believe this addresses everything raised in comments on that patch series. Rich.
2017 Jun 09
12
[PATCH 00/12] Refactor utility functions.
This turned out to be rather more involved than I thought. We have lots of utility functions, spread all over the repository, with not a lot of structure. This moves many of them under common/ and structures them so there are clear dependencies. This doesn't complete the job by any means. Other items I had on my to-do list for this change were: - Split up mllib/common_utils into: -
2017 Jun 12
32
[PATCH v5 00/32] Refactor utilities, implement some APIs in OCaml.
This is a combination of: https://www.redhat.com/archives/libguestfs/2017-June/msg00046.html [PATCH 00/12] Refactor utility functions. plus: https://www.redhat.com/archives/libguestfs/2017-June/msg00023.html [PATCH v3 00/19] Allow APIs to be implemented in OCaml. with the second patches rebased on top of the utility refactoring, and some other adjustments and extensions. This passes
2017 Jun 15
45
[PATCH v6 00/41] Refactor utilities, reimplement inspection in the daemon.
v5: https://www.redhat.com/archives/libguestfs/2017-June/msg00065.html Since v5, this now implements inspection almost completely for Linux and Windows guests. Rich.
2017 Jun 21
45
[PATCH v8 00/42] Refactor utilities and reimplement inspection.
v7 was: https://www.redhat.com/archives/libguestfs/2017-June/msg00169.html https://www.redhat.com/archives/libguestfs/2017-June/msg00184.html I believe this addresses all comments received so far. Also it now passes a test where I compared about 100 disk images processed with old and new virt-inspector binaries. The output is identical in all cases except one which is caused by a bug in blkid