texlive_base failed to build

[Ryan Schmidt]

On Oct 18, 2008, at 14:30, Frank J. R. Hanstick wrote:

> On Oct 18, 2008, at 12:25 PM, Ryan Schmidt wrote:
>
>> On Oct 18, 2008, at 11:51, Frank J. R. Hanstick wrote:
>>
>>> 	I completely uninstalled texlive and texlive_base and then  
>>> installed
>>> using the -d and outputting to a log file.  As I previously noted  
>>> and
>>> subsequently suspected,, xetexdir/XeTeXFontMgr_Mac.mm is the only
>>> file that uses an unprefixed gcc to compile.  The log file
>>> verification is as follows:
>>>
>>> gcc -ObjC++ -I../../libs/icu-xetex/common -I./../../libs/icu-xetex/
>>> common -I./../../libs/icu-xetex/layout -DLE_USE_CMEMORY -I/opt/ 
>>> local/
>>> include -I/opt/local/include/freetype2 -DHAVE_CONFIG_H  -I. -I. -
>>> I.. -
>>> I./..  -isystem/opt/local/include -I../../libs/obsdcompat -I../../
>>> libs/obsdcompat/.. -I./../../libs/obsdcompat -I./../../libs/
>>> obsdcompat/..  -DXETEX_MAC -c xetexdir/XeTeXFontMgr_Mac.mm -o
>>> XeTeXFontMgr_Mac.o
>>>
>>> 	The situations is that with /opt/local/bin at the head of the path,
>>> the search for gcc will result in the /opt/local/bin gcc being used
>>> if installed which will be gcc-mt-4.3.2.
>>>
>>> 	To verify that the command is generated during ./configure, I
>>> unpacked texlive_base in my desktop directory, found the directory,
>>> and ensured that Makefile did not exist.  I then ran ./configure and
>>> generated Makefile.  The generated Makefile had the unprefixed
>>> command.  This looks like an author problem because I do not want to
>>> mess around with the creation of Makefile.
>>
>> Ok. Will somebody report this problem to the author of texlive?
>
> 	I do not know who the author is and I am not on their mailing list.

Would you at least file an issue in the MacPorts issue tracker about  
this problem and assign it to the maintainer of texlive_base so that  
he can take it up with the developers?