From: Andrew Lentvorski <bsder@allcaps.org>
To: Marc Kleine-Budde <mkl@pengutronix.de>, linux-can@vger.kernel.org
Subject: Re: Bug on configure ... where to report?
Date: Mon, 02 Mar 2015 14:57:39 -0800 [thread overview]
Message-ID: <54F4EAE3.5090406@allcaps.org> (raw)
In-Reply-To: <54EEDD2F.5080501@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 2570 bytes --]
Tried your patch but I'm missing something, I think. Output included at
bottom.
-a
On 2/26/15, 12:45 AM, Marc Kleine-Budde wrote:
> Which version of debian are you using?
Some form of Wheezy, I think ...
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# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 7.8 (wheezy)
Release: 7.8
Codename: wheezy
> Which versions of autoconf, automake and libtool are you using?
root@beaglebone:~/can-utils# autoconf --version
autoconf (GNU Autoconf) 2.69
root@beaglebone:~/can-utils# automake --version
Useless use of /d modifier in transliteration operator at
/usr/share/automake-1.9/Automake/Wrap.pm line 60.
automake (GNU automake) 1.9.6
root@beaglebone:~/can-utils# libtool --version
libtool (GNU libtool) 2.4.2
> Can you try the patch I just send to the list?
Tried the patch but got this (what am I missing to apply this?):
root@beaglebone:~/can-utils# git apply makefile-patch.diff
fatal: patch with only garbage at line 5
root@beaglebone:~/can-utils# patch <makefile-patch.diff
patch: **** Only garbage was found in the patch input.
root@beaglebone:~/can-utils# cat makefile-patch.diff
diff --git a/GNUmakefile.am b/GNUmakefile.am
index 53dfb4ec47db..580e60d364c2 100644
--- a/GNUmakefile.am
+++ b/GNUmakefile.am
<at> <at> -1,3 +1,5 <at> <at>
+ACLOCAL_AMFLAGS = -I config/m4
+
AM_CPPFLAGS = \
-I$(top_srcdir)/include \
-I$(top_builddir)/include \
diff --git a/configure.ac b/configure.ac
index 2fa16ce35af2..3b695d3aa9ea 100644
--- a/configure.ac
+++ b/configure.ac
<at> <at> -1,8 +1,8 <at> <at>
# -*- Autoconf -*-
# Process this file with autoconf to produce a configure script.
-AC_PREREQ(2.59)
+AC_PREREQ([2.59])
-AC_INIT([can-utils], [trunk], [linux-can <at> vger.kernel.org])
+AC_INIT([can-utils],[trunk],[linux-can <at> vger.kernel.org])
AC_CONFIG_SRCDIR([lib.c])
AC_CONFIG_MACRO_DIR([config/m4])
AC_CONFIG_AUX_DIR([config/autoconf])
<at> <at> -17,13 +17,7 <at> <at> CFLAGS="${CFLAGS} -Wall"
# Checks for programs.
#
AC_PROG_CC
-#AM_MISSING_PROG(PERL, perl, $missing_dir)
-# libtool, old:
-AC_LIBTOOL_WIN32_DLL
-#AC_LIBTOOL_TAGS([])
-AC_PROG_LIBTOOL
-# libtool, new:
-# LT_INIT(win32-dll)
+LT_INIT(win32-dll)
AM_INIT_AUTOMAKE([foreign no-exeext dist-bzip2])
m4_ifdef([AM_SILENT_RULES], [AM_SILENT_RULES([yes]]))
--
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-03-02 22:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-26 0:07 Bug on configure ... where to report? Andrew Lentvorski
2015-02-26 8:45 ` Marc Kleine-Budde
2015-03-02 22:57 ` Andrew Lentvorski [this message]
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=54F4EAE3.5090406@allcaps.org \
--to=bsder@allcaps.org \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).