bugmake - Bugs: bug #16236, po file update conflicts with...

 
 

bug #16236: po file update conflicts with autoconf conventions

Submitted by:  Shaddy Baddah <shaddybaddah>
Submitted on:  Fri 31 Mar 2006 11:09:00 AM UTC  
 
Severity: 3 - NormalItem Group: Documentation
Status: FixedPrivacy: Public
Assigned to: Paul D. Smith <psmith>Open/Closed: Closed
Component Version: 4.0Operating System: Any
Fixed Release: 3.81Triage Status: None

Add a New Comment(Rich Markup)
   

You are not logged in

Please log in, so followups can be emailed to you.

 

Fri 31 Mar 2006 01:32:43 PM UTC, comment #2:

I've added a note to README.cvs that this mode is not supported for building from CVS. If you want to do this you have to build a release first.

Paul D. Smith <psmith>
Project AdministratorIn charge of this item.
Fri 31 Mar 2006 11:16:51 AM UTC, comment #1:

Further information.

After doing a configure and make update in $(srcdir), trying to do a configure in the build directory fails with:

configure: error: source directory already configured; run "make distclean" there first

Doing a make distclean in $(srcdir) corrects this, and configure will now run in the build directory.

You are then back on the conventional track.

Shaddy Baddah <shaddybaddah>
Fri 31 Mar 2006 11:09:00 AM UTC, original submission:

As I know it, the convention for autoconf/automake builds is to follow these steps at command line:

- make a build directory out of the $(srcdir)
- change directory to that build directory
- run the configure script by entering the correct path to it
- run make out of the build directory to build
- run make install out of the build directory to install

I understand that when using CVS, there are some additional bootstrapping tasks before getting to this stage, and README.cvs indicates running autoreconf -i in $(srcdir) to produce the configure script.

However, there is a further bootstrapping task after this, which is make update, that updates the po files. This task, and the configure task in between it are the subject of this report.

As per the "conventional" steps I specified about, I expect to do my configure outside of $(srcdir). But there is no doubt for bootstrapping, a configure "at least" needs to be done in $(srcdir) or else you cannot bootstrap.

This isn't necessarily a bug... but IMO, it is a break with convention that should be acknowledge somewhere, if not enhanced at some point.

Shaddy Baddah <shaddybaddah>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach File(s):
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

CC list is empty

 

Do you think this task is very important?
If so, you can click here to add your encouragement to it.
This task has 0 encouragements so far.

Only logged-in users can vote.

 

Please enter the title of George Orwell's famous dystopian book (it's a date):

 

 

Follow 7 latest changes.

Date Changed By Updated Field Previous Value => Replaced By
Sat 01 Apr 2006 07:21:31 AM UTCpsmithFixed Release4.0=>3.81
Fri 31 Mar 2006 01:32:43 PM UTCpsmithItem GroupNone=>Documentation
  StatusNone=>Fixed
  Assigned toNone=>psmith
  Open/ClosedOpen=>Closed
  Fixed ReleaseNone=>4.0
Fri 31 Mar 2006 11:09:00 AM UTCshaddybaddahCarbon-Copy-=>Added shaddybaddah

Back to the top


Powered by Savane 3.1-cleanup1