texlive_base failed to build

[Frank J. R. Hanstick]

Hello,
	I reconfigured my system to point to gcc-4.0.1 and successfully got  
through texlive.  The installation was completed successfully.

	In going through the sequence I passed you, I noticed the very first  
error line was:

Error: Target org.macports.build returned: shell command " cd "/opt/ 
local/var/macports/build/ 
_opt_local_var_macports_sources_rsync.macports.org_release_ports_tex_tex 
live_base/work/texlive_base-2007" && make all " returned error 2

Since I do not have verbage before this point, I wonder what in gcc- 
mp-4.3.2 would cause this error.  The build did continue after this  
error in any case.  Even then, there were several compilations prior  
to the gcc -OBjC++ call (xetexini.c, xetex0.c, xetex1.c, xetex2.c,  
xetexextra.c, xetexdir/trans.c, xetexdir/XeTeX_ext.c, and xetexdir/ 
XeTeX_mac.c) that used /usr/bin/gcc-4.0 as advertised.  It was only  
when it came time to compile xetexdir/XeTeXFontMgr_Mac.mm that the  
non prefixed gcc  was called instead of the prefixed /usr/bin/ 
gcc-4.0.  This sounds like a make file error which could have  
resulted from running configure.  Can I assume that in your port, you  
use the configure supplied by the authors to create the make files?
Frank

On Oct 18, 2008, at 1:05 AM, Ryan Schmidt wrote:

>
> On Oct 17, 2008, at 18:15, Frank J. R. Hanstick wrote:
>
>> On Oct 17, 2008, at 2:29 PM, Bryan Blackburn wrote:
>>
>>> On Fri, Oct 17, 2008 at 02:03:56PM -0700, Frank J. R. Hanstick said:
>>>
>>>> ~ frank$ gcc_select -l
>>>> Available versions:
>>>> mp-gcc43
>>>>
>>>> ~ frank$ which gcc
>>>> /opt/local/bin/gcc
>>>
>>> Sounds like some part of the texlive_base build process is ignoring
>>> when
>>> port sets CC to /usr/bin/gcc-4.0, but only when compiling that one
>>> file.
>>> Since it's using just a bare 'gcc' it's picking up your MacPorts-
>>> installed
>>> gcc43 which doesn't support the -ObjC++ option (that option is only
>>> available in Apple's gcc).
>>>
>>> For now, you should be able to get it to build by using gcc_select
>>> to use
>>> gcc40, though your '-l' output above doesn't show it, so make sure
>>> you have
>>> the current gcc_select port (0.1_1).
>>
>> 	The path structure points to /opt/local/bin first instead of /usr/
>> bin; therefore, I pickup the gcc_select in /opt/local/bin gcc_select
>> which is what I want so long as I do not hit -obj/C++.  I had read
>> somewhere that MacPort always used /usr/bin/gcc and bypassed
>> gcc_select.  I gather that this is not true.
>
> MacPorts causes Apple's GCC to always be used by setting the CC  
> variable. If the port ignores the CC variable, as some part of  
> texlive_base appears to, then MacPorts cannot guarantee what GCC  
> will be used. This would appear to be a bug in texlive_base which  
> would be best reported to its authors. Or if you can work out a  
> patch to fix it, we can apply the patch in the port, and then  
> report it to the authors of the software.
>
>
>