The FreeType Project - Bugs: bug #23648, configure script does not pass...
You are not allowed to post comments on this tracker with your current authentication level.
bug #23648: configure script does not pass commandline options to builds/unix/configure
Submitter: | None | ||
Submitted: | Fri 20 Jun 2008 08:57:38 AM UTC | ||
Severity: | 3 - Normal | Item Group: | None |
Status: | Fixed | Privacy: | Public |
Assigned to: | wl | Open/Closed: | Closed |
Planned Release: | 2.3.8 |
Jump to the original submission
Sat 05 Jul 2008 06:36:29 AM UTC, comment #9: |
Werner LEMBERG <wl> |
Wed 02 Jul 2008 09:40:30 AM UTC, comment #8: So, perhaps it's caused by an old version of gnumake, and not by an old shell. Xcode 1.5 for Panther has gnumake 3.79 while Xcode 2.5 for Tiger has gnumake 3.80. |
Ryan Carsten Schmidt <ryandesign> |
Wed 02 Jul 2008 09:24:47 AM UTC, comment #7: This bug is affecting Mac OS X 10.3 (Panther) users as well. FreeType 2.3.5 passed configure arguments from configure to builds/unix/configure just fine, but 2.3.6 and 2.3.7 do not. There is no problem for Mac OS X 10.4 (Tiger) and 10.5 (Leopard) users. This is the MacPorts Project's bug for this issue:
|
Ryan Carsten Schmidt <ryandesign> |
Wed 02 Jul 2008 04:38:19 AM UTC, comment #6: I think I've found the problem. Please try the attached version of the top-level configure script. |
Werner LEMBERG <wl> |
Sun 22 Jun 2008 08:01:30 AM UTC, comment #5: Im afraid we're stuck with this shell for legacy reasons |
Anonymous |
Fri 20 Jun 2008 12:48:06 PM UTC, comment #4: Humm, thinking again I believe it's not related to the configure script at all -- the error appears before it is called.
|
Werner LEMBERG <wl> |
Fri 20 Jun 2008 12:34:42 PM UTC, comment #3: If I enter your command line, I get this:
|
Werner LEMBERG <wl> |
Fri 20 Jun 2008 09:20:02 AM UTC, comment #2: Redhat 7.0 (the very old one, I know)
done.
|
Anonymous |
Fri 20 Jun 2008 09:06:11 AM UTC, comment #1: Something must be broken on your system. Please give more details: Which platform? Which shell? |
Werner LEMBERG <wl> |
Fri 20 Jun 2008 08:57:38 AM UTC, original submission:
The root level configure script ignores any commandline options that should be passed to configure
|
Anonymous |
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 11 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2008-07-05 | wl | Status | Need Info | Fixed | |
Open/Closed | Open | Closed | |||
Planned Release | None | 2.3.8 | |||
2008-07-02 | ryandesign | Attached File | - | Added patch-detect.mk.diff, #15986 | |
2008-07-02 | wl | Attached File | - | Added configure, #15981 | |
Status | Works For Me | Need Info | |||
Open/Closed | Closed | Open | |||
2008-06-20 | wl | Status | Need Info | Works For Me | |
Open/Closed | Open | Closed | |||
2008-06-20 | wl | Status | None | Need Info | |
Assigned to | None | wl |
Powered by Savane 3.13-758e.
Corresponding source code
Reason for using $(value ...) is given in the ChangeLog file, date 2007-12-06:
Pass options from one configure script to another as-is
(not expanded). This is needed for options like
--includedir='${prefix}/include'.
Indeed, $(value ...) has been introduced in GNU make 3.80. I wasn't aware of that, and I've updated the documentation accordingly. I have also implemented a check whether a too old version of GNU make is used.
Please test.