Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: Jonathan.rajotte-julien@efficios.com (Jonathan Rajotte Julien)
Subject: [lttng-dev] Compilation error in lttng-tools (version.c)
Date: Tue, 30 Jun 2015 10:21:55 -0400	[thread overview]
Message-ID: <5592A603.9080508@efficios.com> (raw)
In-Reply-To: <B06A27731337844B9C410EFD0660F0FB0F9BF428@eusaamb109.ericsson.se>


Hi,

On 2015-06-29 04:52 PM, Daniel Olivier wrote:
> Hi,
>
> Indeed, I'm running autoconf 2.63:
>
> SC-1:~/trace_ea/foss/lttng-tools # autoconf --version
> autoconf (GNU Autoconf) 2.63
> ...
> SC-1:~/trace_ea/foss/lttng-tools # automake --version
> automake (GNU automake) 1.10.1
> ...
>
> The system is SLES11:
> SC-1:~/trace_ea/foss/lttng-tools # uname -a
> Linux SC-1 3.0.101-0.47.52-default #1 SMP Thu Mar 26 10:55:49 UTC 2015 (0e3c7c8) x86_64 x86_64 x86_64 GNU/Linux
> SC-1:~/trace_ea/foss/lttng-tools # cat /etc/issue
>
> Welcome to SUSE Linux Enterprise Server 11 SP3  (x86_64) - Kernel \r (\l).
>
> Is there a way to check the autoconf version (during configuration), in order to make the error more explicit?

We would add a check for autoconf >= 2.64 during the bootstrap sequence. 
But this not solve the issue for SLES11sp3.
I did find people trying to support both 2.63 and >= 2.64 [1] but it has 
some downside. It might be a way to do it.

One way to solve the issue would be to do daily distribution tarballs 
(signed of course) so you dont have to bootstrap everything.

Cheers !

[1] https://github.com/gdnsd/gdnsd/blob/master/configure.ac


>
> Thanks,
> Dan
>
> -----Original Message-----
> From: Jonathan Rajotte Julien [mailto:Jonathan.rajotte-julien@efficios.com]
> Sent: Monday, June 29, 2015 4:33 PM
> To: lttng-dev at lists.lttng.org
> Subject: Re: [lttng-dev] Compilation error in lttng-tools (version.c)
>
> Hey Daniel,
>
> As you suggested it look like it's not generated on ./configure when it should.
> The problem come from the AC_INIT macro interpretation from Autoconf.
> The AC_INIT macro we currently use was
> introduced in autoconf 2.64. Look like you are running Autoconf 2.63.
>
> AC_INIT 2.63:
> *AC_INIT*(package, version,[bug-report],[tarname])
>
> AC_INIT 2.64:
> *AC_INIT*(package, version,[bug-report],[tarname],[url])
>
> Which distribution are you using?
>
> Cheers !
>
> On 2015-06-29 03:52 PM, Daniel Olivier wrote:
>> I am getting:
>>
>> make[3]: Entering directory `/root/trace_ea/foss/lttng-tools/src/bin/lttng'
>> depbase=`echo commands/version.o | sed 's|[^/]*$|.deps/&|;s|\.o$||'`;\
>>           gcc -DHAVE_CONFIG_H -I../../.. -I../../.. -I../../../src -I../../../include -include config.h  -I../../../include -I../../../src -DINSTALL_BIN_PATH=\""/usr/local/bin"\"   -Wall -g -O2 -g -fno-strict-aliasing -MT commands/version.o -MD -MP -MF $depbase.Tpo -c -o commands/version.o commands/version.c &&\
>>           mv -f $depbase.Tpo $depbase.Po
>> commands/version.c: In function 'create_version':
>> commands/version.c:71: error: 'PACKAGE_URL' undeclared (first use in
>> this function)
>> commands/version.c:71: error: (Each undeclared identifier is reported
>> only once
>> commands/version.c:71: error: for each function it appears in.)
>> make[3]: *** [commands/version.o] Error 1
>>
>> I gather that PACKAGE_URL should get generated by configure step into config.h (or something)...
>>
>> Attached is config.log, but I didn't find that it contained any errors pertaining to this.
>>
>> Anybody ever see this?
>>
>> Thanks,
>> Daniel
>>
>>
>>
>> _______________________________________________
>> lttng-dev mailing list
>> lttng-dev at lists.lttng.org
>> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
> --
> Jonathan R. Julien
> Efficios
>
>
> _______________________________________________
> lttng-dev mailing list
> lttng-dev at lists.lttng.org
> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

-- 
Jonathan R. Julien
Efficios




      reply	other threads:[~2015-06-30 14:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-29 19:52 Daniel Olivier
2015-06-29 20:33 ` Jonathan Rajotte Julien
2015-06-29 20:52   ` Daniel Olivier
2015-06-30 14:21     ` Jonathan Rajotte Julien [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5592A603.9080508@efficios.com \
    --to=jonathan.rajotte-julien@efficios.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox