autogen.sh slightly confused

Bug #440402 reported by Robert Collins
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-common (Ubuntu)
New
Undecided
Unassigned
notify-osd (Ubuntu)
Invalid
Low
Mirco Müller

Bug Description

checking for autoconf >= 2.59...
  testing autoconf2.50... not found.
  testing autoconf... found 2.64

(note the 'wants >2.59, then probes for 2.50)

I suggest trying 'autoconf' first.

Mirco Müller (macslow)
Changed in notify-osd:
assignee: nobody → Mirco Müller (macslow)
importance: Undecided → Low
Revision history for this message
Mirco Müller (macslow) wrote :

It turned out to be actually gnome-common (/usr/bin/gnome-autogen.sh) being the culprit here doing the wrong testing for autoconf.

Changed in notify-osd:
status: New → Confirmed
milestone: none → ubuntu-9.10
Mirco Müller (macslow)
Changed in notify-osd:
status: Confirmed → Invalid
affects: notify-osd → notify-osd (Ubuntu)
Changed in notify-osd (Ubuntu):
milestone: ubuntu-9.10 → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.