[prev in list] [next in list] [prev in thread] [next in thread]
List: macports-users
Subject: Re: Can't upgrade libtool, libedit, or install openssh
From: semaphore45 () yahoo ! com
Date: 2015-11-24 16:59:38
Message-ID: 3136CF0A-405B-4B3D-81A9-CDE54858500D () yahoo ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Hello,
ticket is created:
https://trac.macports.org/ticket/49798
Is the description good enough?
El 23 nov. 2015, a las 20:57, Ryan Schmidt escribió:
>
> > On Nov 23, 2015, at 1:14 PM, semaphore45@yahoo.com wrote:
> >
> >
> > El 22 nov. 2015, a las 23:08, Ryan Schmidt escribió:
> >
> > >
> > > > On Nov 22, 2015, at 9:28 PM, semaphore45@yahoo.com wrote:
> > > >
> > > > Hello to all.
> > > >
> > > > I retried upgrading readline again, and it failed again, at a different port \
> > > > though.
> > >
> > > As far as I can tell from what you've told us, you've already successfully \
> > > upgraded the readline port. It's done.
> >
> > Technically it isn't. The port upgrade readline reports many broken ports and \
> > attempts to repair them. That's where it fails.
>
> readline has been successfully upgraded. After every port install or upgrade, \
> rev-upgrade checks for broken ports. This is what's now failing because some port \
> is broken and can't be rebuilt. But it has nothing to do with readline. You would \
> see the same after upgrading or installing any other port.
>
> > > But when you upgrade or install any port, MacPorts checks if any ports are \
> > > broken, and tries to rebuild them. Maybe it's determined that the volk port is \
> > > broken, is trying to rebuild it, and is failing.
> > >
> > > > Here is the log:
> > > >
> > > > <main.log.bz2>
> > > >
> > > > Your opinion?
> > >
> > > The log is not from a clean build attempt. Read the ticket filing guidelines, \
> > > clean the port, try again, and if it fails again, file a ticket and attach the \
> > > new log.
> > sudo port clean volk
> > then
> > sudo port upgrade volk
> >
> > failed again, and the log is:
> > <main.log>
> >
> > Is this a bug or a misunderstanding on my part?
>
> The first error I see in the log is:
>
> > info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_distfiles \
> > .macports.org_ports_science_volk/volk/work/volk-1.1.1/include/volk/volk_common.h:71:23: \
> > error: x86intrin.h: No such file or directory
>
> Sounds like a bug. The bug might be that volk is not compatible with Snow Leopard's \
> old gcc 4.2 compiler. In any case, please file a bug report.
>
[Attachment #5 (unknown)]
<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; \
-webkit-line-break: after-white-space; \
"><div>Hello, </div><div><br></div><div>ticket is created:</div><div><a \
href="https://trac.macports.org/ticket/49798">https://trac.macports.org/ticket/49798</a></div><div><br></div><div>Is \
the description good enough?</div><div><br></div><div><br></div><br><div><div>El 23 \
nov. 2015, a las 20:57, Ryan Schmidt escribió:</div><br \
class="Apple-interchange-newline"><blockquote type="cite"><div><br><blockquote \
type="cite">On Nov 23, 2015, at 1:14 PM, <a \
href="mailto:semaphore45@yahoo.com">semaphore45@yahoo.com</a> \
wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote \
type="cite"><br></blockquote><blockquote type="cite">El 22 nov. 2015, a las 23:08, \
Ryan Schmidt escribió:<br></blockquote><blockquote \
type="cite"><br></blockquote><blockquote type="cite"><blockquote \
type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote \
type="cite"><blockquote type="cite">On Nov 22, 2015, at 9:28 PM, <a \
href="mailto:semaphore45@yahoo.com">semaphore45@yahoo.com</a> \
wrote:<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote \
type="cite"><blockquote \
type="cite"><br></blockquote></blockquote></blockquote><blockquote \
type="cite"><blockquote type="cite"><blockquote type="cite">Hello to \
all.<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote \
type="cite"><blockquote \
type="cite"><br></blockquote></blockquote></blockquote><blockquote \
type="cite"><blockquote type="cite"><blockquote type="cite">I retried upgrading \
readline again, and it failed again, at a different port \
though.<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote \
type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote \
type="cite">As far as I can tell from what you've told us, you've already \
successfully upgraded the readline port. It's \
done.<br></blockquote></blockquote><blockquote \
type="cite"><br></blockquote><blockquote type="cite">Technically it isn't. The port \
upgrade readline reports many broken ports and attempts to repair them. That's where \
it fails.<br></blockquote><br>readline has been successfully upgraded. After every \
port install or upgrade, rev-upgrade checks for broken ports. This is what's now \
failing because some port is broken and can't be rebuilt. But it has nothing to do \
with readline. You would see the same after upgrading or installing any other \
port.<br><br><br><blockquote type="cite"><blockquote type="cite">But when you upgrade \
or install any port, MacPorts checks if any ports are broken, and tries to rebuild \
them. Maybe it's determined that the volk port is broken, is trying to rebuild it, \
and is failing.<br></blockquote></blockquote><blockquote type="cite"><blockquote \
type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote \
type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote \
type="cite"><blockquote type="cite">Here is the \
log:<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote \
type="cite"><blockquote \
type="cite"><br></blockquote></blockquote></blockquote><blockquote \
type="cite"><blockquote type="cite"><blockquote \
type="cite"><main.log.bz2><br></blockquote></blockquote></blockquote><blockquote \
type="cite"><blockquote type="cite"><blockquote \
type="cite"><br></blockquote></blockquote></blockquote><blockquote \
type="cite"><blockquote type="cite"><blockquote type="cite">Your \
opinion?<br></blockquote></blockquote></blockquote><blockquote \
type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote \
type="cite"><blockquote type="cite">The log is not from a clean build attempt. Read \
the ticket filing guidelines, clean the port, try again, and if it fails again, file \
a ticket and attach the new log.<br></blockquote></blockquote><blockquote \
type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote \
type="cite">sudo port clean volk<br></blockquote><blockquote \
type="cite">then<br></blockquote><blockquote type="cite">sudo port upgrade \
volk<br></blockquote><blockquote type="cite"><br></blockquote><blockquote \
type="cite">failed again, and the log is:<br></blockquote><blockquote \
type="cite"><main.log><br></blockquote><blockquote \
type="cite"><br></blockquote><blockquote type="cite">Is this a bug or a \
misunderstanding on my part?<br></blockquote><br>The first error I see in the log \
is:<br><br>:info:build \
/opt/local/var/macports/build/_opt_local_var_macports_sources_distfiles.macports.org_ports_science_volk/volk/work/volk-1.1.1/include/volk/volk_common.h:71:23: \
error: x86intrin.h: No such file or directory<br><br>Sounds like a bug. The bug might \
be that volk is not compatible with Snow Leopard's old gcc 4.2 compiler. In any case, \
please file a bug report.<br><br><br></div></blockquote></div><br></body></html>
_______________________________________________
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic