On Mon, Nov 03, 2014 at 03:58:14PM +0530, Lakshmi M wrote:
Can anyone please let me know how to use c++ compiler as default for
compiling my c files.
One way would be to have, anywhere in your makefiles:
CC = $(CXX)
That would compile *all* C as C++.
signature.asc
Description: Digital
your Changelog file is.
Hint: look at the casing of your file name.
--
Pippijn van Steenhoven
signature.asc
Description: Digital signature
On Thu, Jul 24, 2014 at 4:48 PM, Steffen Dettmer steffen.dett...@gmail.com
wrote:
Hi,
I have a test that generates a log file, which I can manually run via
make check. Is there a simple way to automate that? For the moment I
just created a pragmatic target autotest, but I think it is ugly
project. Are you
sure that libcttp2.la exists in $(libdir)? As an experiment, try make
install in libctpp2's $(builddir) and then make install in
$(top_builddir).
Regards,
--
Pippijn van Steenhoven
signature.asc
Description: Digital signature
and write the actual ${dir}_LTLIBRARIES to an included .am
file. Semantically, this is what I do. In reality, I wrote a preprocessor
for automake that does this, but I don't suggest using it, as it's beta
and very much tailored to my needs.
Cheers,
--
Pippijn van Steenhoven
signature.asc
Description
Hi,
in some of my projects, I use (reentrant) flex with the header-file
option. This causes flex to generate a .h file in addition to the usual
lex.yy.c file. However, ylwrap doesn't know about this. What would be the
correct way to use flex with header files?
Regards,
--
Pippijn van Steenhoven
On Sat, Mar 19, 2011 at 10:38:39AM +0100, Pippijn van Steenhoven wrote:
On Fri, Mar 18, 2011 at 05:26:58PM -0700, Harlan Stenn wrote:
If there was a student interested in showing how easy it was to use
automake to do non-recursive Makefiles for a project, I'd be willing to
co-mentor
. How hard are GSoC projects supposed to be?
--
Pippijn van Steenhoven
signature.asc
Description: Digital signature
On Sat, Mar 19, 2011 at 10:38:39AM +0100, Pippijn van Steenhoven wrote:
On Fri, Mar 18, 2011 at 05:26:58PM -0700, Harlan Stenn wrote:
If there was a student interested in showing how easy it was to use
automake to do non-recursive Makefiles for a project, I'd be willing to
co-mentor
of suspecting a bug
in the make implementation, or we're overlooking something with
one-shell issues.
I am using FreeBSD 8.0-RELEASE-p4.
--
Pippijn van Steenhoven
signature.asc
Description: Digital signature
trigger the inference rule .c.lo. Perhaps a solution would
be to also generate explicit rules for built sources.
I have attached the output of running make with and without -j1.
Regards,
Pippijn van Steenhoven
make V=1 axl.lo
/bin/sh ../autoconf/ylwrap `test -f 'src/compiler/phases/parse/axl.y
= foo \
# this is ok \
# - Unassociated shell command
Also, it will break $(am__append*) variables, but that is not relevant in
this case.
--
Pippijn van Steenhoven
signature.asc
Description: Digital signature
agree, but if you mean edge coverage, I don't know how you want to
achieve this. Any O(x) where x1 algorithm anywhere in the code makes it
impossible. If I'm wrong, I'd like to know how Stefano produces it.
--
Pippijn van Steenhoven
signature.asc
Description: Digital signature
agree, but if you mean edge coverage, I don't know how you want to
achieve this. Any O(x) where x1 algorithm anywhere in the code makes it
impossible. If I'm wrong, I'd like to know how Stefano produces it.
--
Pippijn van Steenhoven
signature.asc
Description: Digital signature
On Thu, Nov 11, 2010 at 09:54:35PM +0100, Ralf Wildenhues wrote:
In other words, I can't make dist even with GNU make 3.82? What do you
suggest, then?
Well, you could try my patch from
http://article.gmane.org/gmane.comp.gnu.make.bugs/4219
(append /raw to the URL to get it unmangled).
On Tue, Nov 09, 2010 at 10:37:24AM -0700, Bob Proulx wrote:
Pippijn van Steenhoven wrote:
I am root on my (Linux) system and I set the stack size to unlimited. The
libtool macro reported a few billion (or something other really large)
for maximum argument list length, bash also agreed
On Mon, Nov 08, 2010 at 10:11:20PM +0100, Pippijn van Steenhoven wrote:
make distdir fails. The Makefile.am is not a single file. A combined
file is here: http://paste.xinu.at/ou4jy/, but I'm not sure that is very
useful. A tarball with all .am files is here: http://paste.xinu.at/TzadQ
files
and check files in a different file and reading this with xargs $file
would help.
Any other ideas?
--
Pippijn van Steenhoven
signature.asc
Description: Digital signature
On Mon, Nov 08, 2010 at 08:03:06PM +0100, Ralf Wildenhues wrote:
* Pippijn van Steenhoven wrote on Mon, Nov 08, 2010 at 04:55:45PM CET:
I looked through the mailing list archives and found several questions
and proposed solutions related to this problem:
- Split up file lists so
with GNU make 3.82? What do you
suggest, then?
--
Pippijn van Steenhoven
signature.asc
Description: Digital signature
On Mon, Nov 08, 2010 at 03:03:59PM -0500, Paul Smith wrote:
On Mon, 2010-11-08 at 21:01 +0100, Pippijn van Steenhoven wrote:
I am root on my (Linux) system and I set the stack size to unlimited.
The libtool macro reported a few billion (or something other really
large) for maximum argument
inclusions will be correct (solves your problem) and it automatically
allows for multiple yacc files to coexist in one project.
--
Pippijn van Steenhoven
signature.asc
Description: Digital signature
and #includes. It doesn't know ylwrap renamed it. You
are supposed to say %defines myparser.h or pass bison a -o option so it
produces myparser.c and myparser.h in the first place.
--
Pippijn van Steenhoven
signature.asc
Description: Digital signature
will soon be in git?
--
Pippijn van Steenhoven
signature.asc
Description: Digital signature
the
scgparser.cc is compiled. What am I missing here?
I solved this problem by adding my own y.tab.h which does nothing but
#include scgparser.h.
--
Pippijn van Steenhoven
signature.asc
Description: Digital signature
bother renaming flex-generated header files,
either.
--
Pippijn van Steenhoven
signature.asc
Description: Digital signature
On Sun, Oct 31, 2010 at 10:55:53PM +, Philip Herron wrote:
Your bison file shouldnt generate any code with includes y.tab.h. You
must have it in your field delcarations for bison. Its only your lexer
needs to see these bison definitions.
It does for GLR parsers.
--
Pippijn van Steenhoven
27 matches
Mail list logo
