Can't upgrade libtool, libedit, or install openssh

[semaphore45 at yahoo.com]

Hello to all.

I retried upgrading readline again, and it failed again, at a different port though.

Here is the log:

-------------- next part --------------
A non-text attachment was scrubbed...
Name: main.log.bz2
Type: application/x-bzip2
Size: 4297 bytes
Desc: not available
URL: <https://lists.macosforge.org/pipermail/macports-users/attachments/20151122/f32e6b07/attachment.bz2>
-------------- next part --------------


Your opinion?



El 22 nov. 2015, a las 19:22, Ryan Schmidt escribi?:


> 
>> On Nov 20, 2015, at 8:55 AM, semaphore45 at yahoo.com wrote:
>> 
>> Hello, 
>> 
>> I did try to run 
>> 
>> sudo port upgrade readline
>> 
>> But after long hours of compiling, it failed, again, when trying to upgrade libgcc. 
> 
> To clarify: the original problem of upgrading libtool and libedit and installing openssh due to readline being linked to the old ncurses has been resolved by upgrading readline. You are now experiencing a new unrelated problem, with libgcc.
> 
> 
>>> Error: org.macports.build for port libgcc returned: command execution failed
>>> Please see the log file for port libgcc for details:
>>>    /opt/local/var/macports/logs/_opt_local_var_macports_sources_distfiles.macports.org_ports_lang_gcc5/libgcc/main.log
>> 
>> The end of the error log shows:
>> 
>>> :info:build make[1]: *** [stage3-bubble] Error 2
>>> :info:build make: *** [bootstrap] Error 2
>>> :error:build org.macports.build for port libgcc returned: command execution failed
>>> :debug:build Error code: CHILDSTATUS 96327 2
>> 
>> From the Internet, it seems to be a rather generic error that was corrected. As linked here https://trac.macports.org/ticket/25091, should I try again running it with the -d flag to get more details about the failure?
> 
> No need: Everything you would see using the -d flag is already contained within the main.log file you uploaded.
> 
> It looks like the relevant error message in the log is:
> 
> :info:build configure: error: computing SEEK_CUR failed
> 
> Unfortunately, I don't know why computing SEEK_CUR failed. Several previous configure script runs in your log file show that it was able to determine that the value of SEEK_CUR is 1, so nothing should have needed to be computed.
> 
>