Opened 9 years ago

Closed 9 years ago

#156 closed defect (fixed)

get.Metis script fails when applying patch

Reported by: PGherardi Owned by: ipopt-team
Priority: normal Component: Ipopt
Version: 3.9 Severity: normal
Keywords: Cc:

Description

Executing the get.Metis script gives the following:

Running script for downloading the source code for the METIS Downloading the source code from glaros.dtc.umn.edu... --2011-04-06 22:41:02-- http://glaros.dtc.umn.edu/gkhome/fetch/sw/metis/metis-4.0.tar.gz Resolving glaros.dtc.umn.edu (glaros.dtc.umn.edu)... 160.94.77.162 Connecting to glaros.dtc.umn.edu (glaros.dtc.umn.edu)|160.94.77.162|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 522624 (510K) [application/x-gzip] Saving to: “metis-4.0.tar.gz”

100%[=============================================================================================================================================================>] 522,624 885K/s in 0.6s

2011-04-06 22:41:03 (885 KB/s) - “metis-4.0.tar.gz” saved [522624/522624]

Uncompressing the tarball... Unpacking the source code... Deleting the tar file... Apply patch file... can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was:


metis-4.0.org/Lib/rename.h 2009-07-20 10:02:06.000000000 +0200

|+++ metis-4.0/Lib/rename.h 2009-07-20 10:02:19.000000000 +0200


File to patch: Skip this patch? [y] Skipping patch. 1 out of 1 hunk ignored

Change History (1)

comment:1 Changed 9 years ago by andreasw

  • Resolution set to fixed
  • Status changed from new to closed

Thanks for letting me know. I just created a new Ipopt release 3.9.3, which has the latest ThirdParty/Metis? that can deal with the change in the metis tarball.

Note: See TracTickets for help on using tickets.