helpGNU gettext - Support: sr #108469, gettext-0.18.3.1: libintl hard...

 
 

sr #108469: gettext-0.18.3.1: libintl hard codes potentially invalid path

Submitted by:  Keith Marshall <keithmarshall>
Submitted on:  Thu 09 Jan 2014 10:01:07 PM UTC  
 
Category: NonePriority: 5 - Normal
Severity: 3 - NormalStatus: None
Privacy: PublicAssigned to: None
Open/Closed: OpenOperating System: Microsoft Windows

Add a New Comment(Rich Markup)
   

You are not logged in

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

 

Thu 09 Jan 2014 10:58:04 PM UTC, comment #1:

s/potentially removal media/potentially removable media/

Obviously, the issue bites when the hard coded path points to a removable media device, in which no media is present. Woe32 then requires the user to insert media when a path scan is initiated, even if the search should eventually be resolved elsewhere.

Keith Marshall <keithmarshall>
Thu 09 Jan 2014 10:01:07 PM UTC, original submission:

Identified during this ML discussion:
http://thread.gmane.org/gmane.comp.gnu.mingw.devel/5366

hard-coded paths incorporated into libintl provide the probable vector for this MinGW bug:
https://sourceforge.net/p/mingw/bugs/2108/

As noted in the ML thread, when I rebuild gettext-0.18.3.1, cross compiling on GNU/Linux for the Woe32 host, I see two instances of the hard coded path "/mingw/share/locale" within this library. While this likely will not fall foul of the issue, where the original packager had this prefixed by a drive reference, to a device with potentially removal media, is it expected that this path should be hard coded in the first instance? How does this interact with the relocation machinery, which I understand to be an inherent feature of GNU gettext? Should configuration with the "--enable-relocatable" option affect this? (It seems to make no difference).

In addition, it has been suggested that we consider this patch:
https://sourceforge.net/p/mingw/bugs/1808/

to add relocation support to gettext-0.18.3.1. Am I missing something here? AIUI, gettext already provides relocation support, so why should we need a patch to add it?

Keith Marshall <keithmarshall>

 

(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

 

Carbon-Copy List
  • -unavailable- added by keithmarshall (Submitted the item)
  •  

    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):

     

     

    No Changes Have Been Made to This Item

    Back to the top


    Powered by Savane 3.1-cleanup1