Opened 12 years ago

Closed 12 years ago

Last modified 12 years ago

#37319 closed defect (worksforme)

nmap: checking whether /opt/local/bin/python2.7 version >= 2.4... configure: error: too old

Reported by: monkam-l@… Owned by: opendarwin.org@…
Priority: Normal Milestone:
Component: ports Version: 2.1.2
Keywords: Cc: danielluke (Daniel J. Luke)
Port: nmap

Description (last modified by ryandesign (Ryan Carsten Schmidt))

after uninstall the port nmap with zenmap I try to re install it but unfurtunaly get an error I already clean the port 10 times and nothing work

thank for the help

# sudo port install nmap +zenmap
  --->  Computing dependencies for nmap
  --->  Configuring nmap
  Error: org.macports.configure for port nmap returned: configure failure: command execution failed
  Please see the log file for port nmap for details:
      /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_net_nmap/nmap/main.log
  To report a bug, follow the instructions in the guide:
      http://guide.macports.org/#project.tickets
  Error: Processing of port nmap failed

Attachments (2)

main.log (92.3 KB) - added by monkam-l@… 12 years ago.
main.2.log (14.7 KB) - added by monkam-l@… 12 years ago.

Download all attachments as: .zip

Change History (18)

Changed 12 years ago by monkam-l@…

Attachment: main.log added

comment:1 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: dluke@… added
Description: modified (diff)
Owner: changed from macports-tickets@… to opendarwin.org@…
Port: nmap added
Summary: Error: org.macports.configure for port nmap returned: configure failure: command execution failednmap: checking whether /opt/local/bin/python2.7 version >= 2.4... configure: error: too old
Type: requestdefect

The interesting line in the log is:

:info:configure checking whether /opt/local/bin/python2.7 version >= 2.4... configure: error: too old

Obviously the version of /opt/local/bin/python2.7 should be >= 2.4 but for some reason configure doesn't think it isn't.

Could you attach the config.log file? It might shed some light on why this check failed. It should be located under the directory identified by this command:

port work nmap

comment:2 Changed 12 years ago by monkam-l@…

there is no file in the directory

comment:3 Changed 12 years ago by monkam-l@…

the command upgrade outdated give me this error whats wrong with my macports ??

port upgrade outdated

---> Computing dependencies for gobject-introspection ---> Configuring gobject-introspection Error: org.macports.configure for port gobject-introspection returned: configure failure: command execution failed Please see the log file for port gobject-introspection for details:

/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_gnome_gobject-introspection/gobject-introspection/main.log

Error: Unable to upgrade port: 1 To report a bug, follow the instructions in the guide:

http://guide.macports.org/#project.tickets

ntrospection/work/gobject-introspection-1.34.1.1 gobject-introspection/gobject-i

comment:4 in reply to:  2 Changed 12 years ago by danielluke (Daniel J. Luke)

Replying to monkam-l@…:

there is no file in the directory

Did you perhaps run port clean after your failed build?

It's going to be very difficult (or impossible) to figure out what is going on without some more information on why that configure test failed.

comment:5 in reply to:  3 Changed 12 years ago by danielluke (Daniel J. Luke)

Replying to monkam-l@…:

port upgrade outdated

---> Computing dependencies for gobject-introspection ---> Configuring gobject-introspection Error: org.macports.configure for port gobject-introspection returned: configure failure: command execution failed Please see the log file for port gobject-introspection for details:

/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_gnome_gobject-introspection/gobject-introspection/main.log

Error: Unable to upgrade port: 1 To report a bug, follow the instructions in the guide:

http://guide.macports.org/#project.tickets

ntrospection/work/gobject-introspection-1.34.1.1 gobject-introspection/gobject-i

That doesn't appear to be related to nmap - if you can't determine what has gone wrong (perhaps by looking at the main.log) you should follow the instructions printed out in that error message.

comment:6 Changed 12 years ago by monkam-l@…

so what should I do if there is no instruction printed and if there is no log ??

thanks for any help

comment:7 in reply to:  6 Changed 12 years ago by danielluke (Daniel J. Luke)

Replying to monkam-l@…:

so what should I do if there is no instruction printed

There were instructions printed in the output you pasted above.

and if there is no log ??

for the nmap problem, clean and try again - if it fails, check it immediately and there will be a log file there.

comment:8 Changed 12 years ago by monkam-l@…

or how can I unistall macports clean ???

so I can try a reinstall and build all again if there is no help

comment:9 Changed 12 years ago by monkam-l@…

which line is an instruction I am to dump to see it sorry

comment:10 in reply to:  8 ; Changed 12 years ago by danielluke (Daniel J. Luke)

Replying to monkam-l@…:

or how can I unistall macports clean ???

I don't think you need to (and I don't think it will help you), but:

http://guide.macports.org/#installing.macports.uninstalling

comment:11 in reply to:  10 Changed 12 years ago by monkam-l@…

Replying to dluke@…:

Replying to monkam-l@…:

or how can I unistall macports clean ???

I don't think you need to (and I don't think it will help you), but:

http://guide.macports.org/#installing.macports.uninstalling

I am tired of getting error I am only a noob who try to learn it but I think the best way is to start again I believe the macports data are bugy after I done something wrong do not know what I did wrong but in fact I get error by typing simple command

comment:12 Changed 12 years ago by danielluke (Daniel J. Luke)

Resolution: worksforme
Status: newclosed

Changed 12 years ago by monkam-l@…

Attachment: main.2.log added

comment:13 Changed 12 years ago by monkam-l@…

why is the status closed

Version 0, edited 12 years ago by monkam-l@… (next)

comment:14 in reply to:  13 ; Changed 12 years ago by danielluke (Daniel J. Luke)

Replying to monkam-l@…:

why is the status closed

Because you cannot supply the information necessary to determine what is wrong and you're planning on deleting everything and starting over anyway.

comment:15 in reply to:  14 ; Changed 12 years ago by monkam-l@…

Replying to dluke@…:

Replying to monkam-l@…:

why is the status closed

Because you cannot supply the information necessary to determine what is wrong and you're planning on deleting everything and starting over anyway.

Ok litlle info abut it would be nice thank you for the help

comment:16 in reply to:  15 Changed 12 years ago by danielluke (Daniel J. Luke)

Replying to monkam-l@…:

Ok litlle info abut it would be nice thank you for the help

trac is for bugs, if you want support please use the mailing list.

Note: See TracTickets for help on using tickets.