ispell should check if POSIX functionality is available in the system libraries 
before trying to provide its own version.

On Jul 1, 2011, at 2:52 AM, Ryan Schmidt wrote:

> On Jun 28, 2011, at 14:01, Artemio Gonzalez Lopez wrote:
> 
>> When trying to compile ispell under Lion (latest build), I got the following 
>> error:
>> 
>> /Developer/usr/bin/llvm-gcc-4.2 -O -c term.c
>> + /Developer/usr/bin/llvm-gcc-4.2 -O -c ispell.c
>> + /Developer/usr/bin/llvm-gcc-4.2 -O -c correct.c
>> correct.c:248: error: conflicting types for 'getline'
>> /usr/include/stdio.h:449: error: previous declaration of 'getline' was here
>> make: *** [correct.o] Error 1
>> shell command " cd 
>> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_textproc_ispell/work/ispell-3.3.02"
>>  && /usr/bin/make all " returned error 2
>> Error: Target org.macports.build returned: shell command failed (see log for 
>> details)
>> DEBUG: Backtrace: shell command failed (see log for details)
>>   while executing
>> "command_exec build"
>>   (procedure "portbuild::build_main" line 8)
>>   invoked from within
>> "$procedure $targetname"
>> Warning: the following items did not execute (for ispell): 
>> org.macports.activate org.macports.build org.macports.destroot 
>> org.macports.install
>> Log for ispell is at: 
>> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_textproc_ispell/main.log
>> Error: Status 1 encountered during processing.
> 
> I'm not sure. It builds fine for me on Snow Leopard with Xcode 3.2.6 with 
> either the default gcc-4.2 compiler or with llvm-gcc-4.2. So what you're 
> seeing may be specific to the llvm-gcc-4.2 in your version of Xcode, or 
> specific to Lion or the pre-release of it that you're running. We'll probably 
> have to wait until Lion is released to the public; either this is an Apple 
> problem they'll fix by then, or then we'll be able to get our hands on it and 
> try to fix it. You could also email the developers of ispell about the 
> problem and see if they have any ideas. (MacPorts has nobody maintaining the 
> ispell port.)
> 
> 
> _______________________________________________
> macports-users mailing list
> macports-users@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
> 

_______________________________________________
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Reply via email to