Skip to contentSkip to conversation

Autotools and "foreign"

DISCUSSION Mike Looijmans 3 participants 5 messages Aug 12, 2014 – Aug 13, 2014

lore
Share & tools
lore
#0 lore raw

I tried to upgrade to the current master, and got a few dozen packages now failing to build because of automake errors like this:

| Makefile.am: error: required file './NEWS' not found
| Makefile.am: error: required file './README' not found
| Makefile.am: error: required file './AUTHORS' not found

This apparently traces down to:
74b05bba64589da0e4439a4293559ad9670104bd "autoconf: remove automake patch enforcing --foreign"

Is there an alternative to manually patching all of these packages to get them to compile once more?

Signature · 1 line
Mike Looijmans
#1 lore raw
Quoted 2 lines · Mike Looijmans

Is there an alternative to manually patching all of these packages to get them to compile once more?

Depends on the package, but generally you'll need to update the automake macro at the top of configure.ac (and submit a patch upstream as this should have been fixed years ago).

Encouraging said upstreams to use autoreconf instead of (likely) home-grown crazy would be a good move whilst you're talking to them.

Ross

#2 lore raw
Quoted 7 lines · Ross
Quoted 2 lines · Mike Looijmans

Is there an alternative to manually patching all of these packages to get them to compile once more?

Depends on the package, but generally you'll need to update the automake macro at the top of configure.ac (and submit a patch upstream as this should have been fixed years ago).

Basically, you're saying "no" then?

Quoted 2 lines

Encouraging said upstreams to use autoreconf instead of (likely) home-grown crazy would be a good move whilst you're talking to them.

That might be the case if said upstream people actually still existed. Most of these packages have since long been abandoned.

So I guess I'll have to cook up a class that works around it, just adding the "missing" files into the S directory might do the trick.

Mike.

Met vriendelijke groet / kind regards,

Mike Looijmans

TOPIC Embedded Systems Eindhovenseweg 32-C, NL-5683 KH Best Postbus 440, NL-5680 AK Best
Telefoon: (+31) (0) 499 33 69 79
Telefax: (+31) (0) 499 33 69 70
E-mail: [email protected]
Website: www.topic.nl

Please consider the environment before printing this e-mail

Bezoek ons op 9 en 10 september tijdens Technology for Health Den Bosch (stand 53)
http://www.technologyforhealth.nl

#3 lore raw
Quoted 11 lines · Mike Looijmans
Quoted 7 lines · Ross
Quoted 2 lines · Mike Looijmans

Is there an alternative to manually patching all of these packages to get them to compile once more?

Depends on the package, but generally you'll need to update the automake macro at the top of configure.ac (and submit a patch upstream as this should have been fixed years ago).

Basically, you're saying "no" then?

Quoted 9 lines
Quoted 2 lines

Encouraging said upstreams to use autoreconf instead of (likely) home-grown crazy would be a good move whilst you're talking to them.

That might be the case if said upstream people actually still existed. Most of these packages have since long been abandoned.

So I guess I'll have to cook up a class that works around it, just adding the "missing" files into the S directory might do the trick.

How about add this to configure.ac:

AM_INIT_AUTOMAKE([foreign])

// Robert

Quoted 20 lines

Mike.

Met vriendelijke groet / kind regards,

Mike Looijmans

TOPIC Embedded Systems
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: (+31) (0) 499 33 69 79
Telefax: (+31) (0) 499 33 69 70
E-mail: [email protected]
Website: www.topic.nl

Please consider the environment before printing this e-mail

Bezoek ons op 9 en 10 september tijdens Technology for Health Den Bosch (stand 53)
http://www.technologyforhealth.nl

#4 lore raw
In reply to Mike Looijmans
Quoted 2 lines · Mike Looijmans

That might be the case if said upstream people actually still existed. Most of these packages have since long been abandoned.

That's generally where the problems are - packages that expect autotools from ten years ago.

Quoted 2 lines

So I guess I'll have to cook up a class that works around it, just adding the "missing" files into the S directory might do the trick.

In my experience of fixing oe-core, most packages that fail here already have patches to fix their autotools infrastructure, so adding [foreign] is just another fix in the same patch.

Ross