Opened 11 years ago

Closed 11 years ago

Last modified 10 years ago

#40146 closed defect (invalid)

gnutls @3.1.10_0: build failure

Reported by: adsvrsqueiroz@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 2.2.0
Keywords: Cc: axet (Alexey Kuznetsov)
Port: gnutls

Description (last modified by larryv (Lawrence Velázquez))

dear nice day,

I recently installed the mac osx 10.9, after that I started having problems with my mac ports, managed to upgrade to 2.2.0 but macports to complete the process must give the command sudo port upgrade outdated, ai at the end it's bug in gnutls, tried to understand the error but I can not. Below is a log of it:

`/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_gnutls/gnutls/work/gnutls-3.1.10/src'
:info:build make[1]: *** [all-recursive] Error 1
:info:build make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_gnutls/gnutls/work/gnutls-3.1.10'
:info:build make: *** [all] Error 2
:info:build make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_gnutls/gnutls/work/gnutls-3.1.10'
:info:build Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_gnutls/gnutls/work/gnutls-3.1.10" && /usr/bin/make -j4 -w all 
:info:build Exit code: 2
:error:build org.macports.build for port gnutls returned: command execution failed
:debug:build Error code: CHILDSTATUS 17687 2
:debug:build Backtrace: command execution failed
    while executing
"system -nice 0 $fullcmdstring"
    ("eval" body line 1)
    invoked from within
"eval system $notty $nice \$fullcmdstring"
    invoked from within
"command_exec build"
    (procedure "portbuild::build_main" line 8)
    invoked from within
"$procedure $targetname"
:info:build Warning: targets not executed for gnutls: org.macports.destroot org.macports.build
:notice:build Please see the log file for port gnutls for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_gnutls/gnutls/main.log

Attachments (1)

gnutls.log (482.3 KB) - added by adsvrsqueiroz@… 11 years ago.
LOG GNUTLS

Download all attachments as: .zip

Change History (9)

Changed 11 years ago by adsvrsqueiroz@…

Attachment: gnutls.log added

LOG GNUTLS

comment:1 Changed 11 years ago by larryv (Lawrence Velázquez)

Description: modified (diff)
Keywords: GNUTLS removed
Port: gnutls added; GNUTLS removed
Summary: gnutlsgnutls @3.1.10_0: build failure
Type: updatedefect

This is the actual error.

:info:build /bin/sh ../../libtool  --tag=CC   --mode=link /usr/bin/clang  -pipe -Os -arch x86_64  -L/opt/local/lib -Wl,-headerpad_max_install_names -arch x86_64 -o crywrap crywrap.o ../../lib/libgnutls.la ../../gl/libgnu.la -lidn 
:info:build libtool: link: cannot find the library `/opt/local/lib/libintl.la' or unhandled argument `/opt/local/lib/libintl.la'
:info:build make[4]: *** [crywrap] Error 1

Did you reinstall MacPorts after upgrading your OS, as per the Migration instructions?

comment:2 in reply to:  1 Changed 11 years ago by adsvrsqueiroz@…

updated the system when I ran the command sudo port-d selfupdate instead of following the migration procedure.

Replying to larryv@…:

This is the actual error.

:info:build /bin/sh ../../libtool  --tag=CC   --mode=link /usr/bin/clang  -pipe -Os -arch x86_64  -L/opt/local/lib -Wl,-headerpad_max_install_names -arch x86_64 -o crywrap crywrap.o ../../lib/libgnutls.la ../../gl/libgnu.la -lidn 
:info:build libtool: link: cannot find the library `/opt/local/lib/libintl.la' or unhandled argument `/opt/local/lib/libintl.la'
:info:build make[4]: *** [crywrap] Error 1

Did you reinstall MacPorts after upgrading your OS, as per the Migration instructions?

comment:3 Changed 11 years ago by adsvrsqueiroz@…

updated the system when I ran the command sudo port-d selfupdate instead of following the migration procedure

comment:4 in reply to:  3 ; Changed 11 years ago by larryv (Lawrence Velázquez)

Replying to adsvrsqueiroz@…:

updated the system when I ran the command sudo port-d selfupdate instead of following the migration procedure

That is insufficient. After you update your OS, you must reinstall MacPorts and your ports from scratch, due to the many behavioral vagaries exhibited by new operating systems. Please do this now, or we will not provide further support.

(This is especially true for MacPorts 2.2 on Mavericks, as we have made changes to the way we handle libtool archives. [Namely, we delete them.] These changes require all ports to be rebuilt.)

comment:5 in reply to:  4 ; Changed 11 years ago by adsvrsqueiroz@…

OK will do the procedure, and anything inform

Replying to larryv@…:

Replying to adsvrsqueiroz@…:

updated the system when I ran the command sudo port-d selfupdate instead of following the migration procedure

That is insufficient. After you update your OS, you must reinstall MacPorts and your ports from scratch, due to the many behavioral vagaries exhibited by new operating systems. Please do this now, or we will not provide further support.

(This is especially true for MacPorts 2.2 on Mavericks, as we have made changes to the way we handle libtool archives. [Namely, we delete them.] These changes require all ports to be rebuilt.)

comment:6 in reply to:  5 ; Changed 11 years ago by adsvrsqueiroz@…

Thank you for information, now its OK.

Replying to adsvrsqueiroz@…:

OK will do the procedure, and anything inform

Replying to larryv@…:

Replying to adsvrsqueiroz@…:

updated the system when I ran the command sudo port-d selfupdate instead of following the migration procedure

That is insufficient. After you update your OS, you must reinstall MacPorts and your ports from scratch, due to the many behavioral vagaries exhibited by new operating systems. Please do this now, or we will not provide further support.

(This is especially true for MacPorts 2.2 on Mavericks, as we have made changes to the way we handle libtool archives. [Namely, we delete them.] These changes require all ports to be rebuilt.)

comment:7 in reply to:  6 Changed 11 years ago by larryv (Lawrence Velázquez)

Resolution: invalid
Status: newclosed

Replying to adsvrsqueiroz@…:

Thank you for information, now its OK.

Excellent.

comment:8 Changed 10 years ago by axet (Alexey Kuznetsov)

Cc: axet@… added

Cc Me!

Note: See TracTickets for help on using tickets.