All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Lentvorski <bsder@allcaps.org>
To: linux-can@vger.kernel.org
Subject: Bug on configure ... where to report?
Date: Wed, 25 Feb 2015 16:07:33 -0800	[thread overview]
Message-ID: <54EE63C5.3040307@allcaps.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 3349 bytes --]

I pulled the can-utils from gitorious and am trying to build them up on
a Beaglebone Black Debian but am getting errors when I try to run
configure.  autogen.sh is also producing warnings.

Where do I file a bug report?

Thanks,
-a



root@beaglebone:~/can-utils# uname -a
Linux beaglebone 3.8.13-bone50 #1 SMP Tue May 13 13:24:52 UTC 2014
armv7l GNU/Linux



root@beaglebone:~/can-utils# ./configure
<...lots deleted...>
checking dependency style of gcc... gcc3
./configure: line 11668: syntax error near unexpected token `)'
./configure: line 11668: `)'




root@beaglebone:~/can-utils# ./autogen.sh

----------
autoreconf
----------

configure.ac:22: warning: The macro `AC_LIBTOOL_WIN32_DLL' is obsolete.
configure.ac:22: You should run autoupdate.
aclocal.m4:8118: AC_LIBTOOL_WIN32_DLL is expanded from...
configure.ac:22: the top level
configure.ac:22: warning: AC_LIBTOOL_WIN32_DLL: Remove this warning and
the call to _LT_SET_OPTION when you
configure.ac:22: put the `win32-dll' option into LT_INIT's first parameter.
aclocal.m4:8118: AC_LIBTOOL_WIN32_DLL is expanded from...
configure.ac:22: the top level
configure.ac:24: warning: The macro `AC_PROG_LIBTOOL' is obsolete.
configure.ac:24: You should run autoupdate.
aclocal.m4:120: AC_PROG_LIBTOOL is expanded from...
configure.ac:24: the top level
configure.ac:28: warning: The macro `AC_FOREACH' is obsolete.
configure.ac:28: You should run autoupdate.
../../lib/autoconf/general.m4:194: AC_FOREACH is expanded from...
aclocal.m4:9254: _AM_SET_OPTIONS is expanded from...
aclocal.m4:8956: AM_INIT_AUTOMAKE is expanded from...
configure.ac:28: the top level
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `config/autoconf'.
libtoolize: copying file `config/autoconf/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `config/m4'.
libtoolize: copying file `config/m4/libtool.m4'
libtoolize: copying file `config/m4/ltoptions.m4'
libtoolize: copying file `config/m4/ltsugar.m4'
libtoolize: copying file `config/m4/ltversion.m4'
libtoolize: copying file `config/m4/lt~obsolete.m4'
libtoolize: Consider adding `-I config/m4' to ACLOCAL_AMFLAGS in
Makefile.am.
configure.ac:22: warning: The macro `AC_LIBTOOL_WIN32_DLL' is obsolete.
configure.ac:22: You should run autoupdate.
aclocal.m4:8118: AC_LIBTOOL_WIN32_DLL is expanded from...
configure.ac:22: the top level
configure.ac:22: warning: AC_LIBTOOL_WIN32_DLL: Remove this warning and
the call to _LT_SET_OPTION when you
configure.ac:22: put the `win32-dll' option into LT_INIT's first parameter.
aclocal.m4:8118: AC_LIBTOOL_WIN32_DLL is expanded from...
configure.ac:22: the top level
configure.ac:24: warning: The macro `AC_PROG_LIBTOOL' is obsolete.
configure.ac:24: You should run autoupdate.
aclocal.m4:120: AC_PROG_LIBTOOL is expanded from...
configure.ac:24: the top level
configure.ac:28: warning: The macro `AC_FOREACH' is obsolete.
configure.ac:28: You should run autoupdate.
../../lib/autoconf/general.m4:194: AC_FOREACH is expanded from...
aclocal.m4:9254: _AM_SET_OPTIONS is expanded from...
aclocal.m4:8956: AM_INIT_AUTOMAKE is expanded from...
configure.ac:28: the top level
Useless use of /d modifier in transliteration operator at
/usr/share/automake-1.9/Automake/Wrap.pm line 60.

--------
Finished
--------




[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

             reply	other threads:[~2015-02-26  0:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-26  0:07 Andrew Lentvorski [this message]
2015-02-26  8:45 ` Bug on configure ... where to report? Marc Kleine-Budde
2015-03-02 22:57   ` Andrew Lentvorski
2015-03-03  6:12     ` Oliver Hartkopp
2015-03-03  7:06       ` Andrew Lentvorski
2015-03-03  7:29     ` Marc Kleine-Budde
2015-03-03 10:30       ` Andrew Lentvorski
2015-02-26  8:47 ` Marc Kleine-Budde

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=54EE63C5.3040307@allcaps.org \
    --to=bsder@allcaps.org \
    --cc=linux-can@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.