build fails after system recovery

Thu Nov 15 09:05:57 PST 2012

Hi all,

I am still trying to find at least the source of this strange behavior. Thus, I did the following:

sudo port -v selfupdate
sudo port clean --all ghostscript
sudo port upgrade outdated
sudo port install cmake ghostscript netcdf

The build still crashes but I get some more information in the log (s. attachment) file. There is one warning generated during the configure-process, which might be a hint:

:info:configure checking for jbig2_page_out in -ljbig2dec... yes
:info:configure configure: WARNING: JBIG2 support requires stdint types which do not seem to be available.

since the compiler crashes at the end with

:info:build In file included from ./base/gpsync.h:22,
:info:build                  from ./base/gp_nsync.c:20:
:info:build ./base/stdint_.h:115: error: conflicting types for ‘int64_t’
:info:build /usr/include/i386/types.h:93: error: previous declaration of ‘int64_t’ was here

Any suggestion?

Cheers,

Stephan

BTW: macports reports ":debug:clean OS darwin/10.8.0 (Mac OS X 10.6) arch i386" which matches my sytstem and "pdf2djvu" isn't involved at all...

Am 15.11.2012 um 13:11 schrieb Stephan Eickschen:

> Hi Nicolas,
> 
> thanks for your advice.
> 
> I am running Snow Leopard (10.6.8) -- at least my system profiler tells this:
> 
>  Systemversion:	Mac OS X 10.6.8 (10K549)
>   Kernel-Version:	Darwin 10.8.0
>   Startvolume:	Macintosh HD
>   Startmodus:	Normal
>   Gerätename:	eule-a2
>   Benutzername:	Stephan Eickschen (stephan)
>   Sicherer virtueller Speicher:	Nicht aktiviert
>   64-Bit-Kernel and -Erweiterungen:	Nein
>   Zeit seit dem Start:	2:36
> 
> Developer Information:
> 
>   Version:	3.2 (10M2518)
>   Location:	/Developer
>   Applications:
>   Xcode:	3.2.6 (1761)
>   Interface Builder:	3.2.6 (851)
>   Instruments:	2.7 (3017)
>   Dashcode:	3.0.2 (333)
>   SDKs:
>   Mac OS X:
>   10.5:	(9L31a)
>   10.6:	(10M2518)
> 
> eule-a2:~ stephan$ uname -a
> Darwin eule-a2.local 10.8.0 Darwin Kernel Version 10.8.0: Tue Jun  7 16:33:36 PDT 2011; root:xnu-1504.15.3~1/RELEASE_I386 i386
> 
> And, yes, the first thing after running the macports install package was to run "sudo port selfupdate"
> 
>   500  sudo port -v selfupdate
>   501  sudo port installed
>   502  sudo port upgrade outdated
>   503  sudo port install cmake ghostscript netcdf
> 
> Cheers,
> 
> Stephan
> 
> Am 15.11.2012 um 12:58 schrieb Nicolas Pavillon:
> 
>> Hello, 
>> 
>> A first weird thing is that the log indicates 
>>> :debug:main OS darwin/11.4.0 (Mac OS X 10.7) arch i386
>> which is not consistent with the OS you gave. In case you are indeed under Lion, the recommended Xcode is 4.3.x and should be obtained from the Apple Developer Connection (see instructions at http://www.macports.org/install.php). 
>> 
>> Secondly, the install breaks at pdf2djvu, where it tries to install version 0.7.13, while the latest version in Macports is 0.7.15. You should run "sudo port selfupdate" after Macports' install to ensure building the latest ports.
>> 
>> Cheers, 
>> 
>> Nicolas
>> 
>> On Nov 15, 2012, at 7:29 PM, Stephan Eickschen <stephan.eickschen at eiskultur.de> wrote:
>> 
>>> Hi all,
>>> 
>>> first my apologies for being a complete macports-newbie.
>>> 
>>> Some days ago I had to recover my entire system from time machine due to this damn Seagate-HDD-iMac-thing: I experienced a complete HDD failure two days before the HDD exchange was planed :-( Most things are up and running again but I can't get macports working again. Well, macports itself works, but building ports fails.
>>> 
>>> * System: iMac running MacOSX 10.6.8
>>> * XCode: 3.2.6 (deinstalled, reinstalled from DVD and patched by Software Update)
>>> * macports deinstalled and reinstalled from MacPorts-2.1.2-10.6-SnowLeopard and "sudo port -d selfupdate" done
>>> 
>>> When running
>>> sudo port install cmake ghostscript netcdf
>>> the process crashes with
>>> 
>>> --->  Building ghostscript
>>> Error: org.macports.build for port ghostscript returned: command execution failed
>>> Please see the log file for port ghostscript for details:
>>>   /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_print_ghostscript/ghostscript/main.log
>>> To report a bug, follow the instructions in the guide:
>>>   http://guide.macports.org/#project.tickets
>>> Error: Processing of port ghostscript failed
>>> 
>>> I attach the named file.
>>> 
>>> For the moment I don't think that this is a bug.
>>> 
>>> Any help appreciated, I hope that I didn't miss something obvious,
>>> regards,
>>> 
>>> Stephan
>>> 
>>> <main.log>_______________________________________________
>>> macports-users mailing list
>>> macports-users at lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo/macports-users
>> 
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20121115/420903d7/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: main.log
Type: application/octet-stream
Size: 128172 bytes
Desc: not available
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20121115/420903d7/attachment.obj>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20121115/420903d7/attachment-0001.html>