Getting the error âgetopt.h:85:29: fatal error: getopt-pfx-core.h: No such file or directoryâ while trying to compile libvirt [closed]
Clash Royale CLAN TAG#URR8PPP
up vote
-1
down vote
favorite
In trying to compile an old version of libvirt (to see if I can get some old patches up to date, see https://www.redhat.com/archives/libvir-list/2014-March/msg00106.html), I get the error:
getopt.h:85:29: fatal error: getopt-pfx-core.h: No such file or directory
when I run make (after running ./autogen.sh).
This is on libvirt commit aa50a5c.
In searching for this error ("fatal error: getopt-pfx-core.h: No such file or directory") I find very few results, but it does not seem specific to libvirt, which makes sense since the error seems to be something with getopt.
compiling libvirt
closed as off-topic by Jeff Schaller, phk, Michael Homer, G-Man, sebasth Jan 22 at 7:43
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions describing a problem that can't be reproduced and seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers." â Jeff Schaller, phk, Michael Homer, G-Man, sebasth
add a comment |Â
up vote
-1
down vote
favorite
In trying to compile an old version of libvirt (to see if I can get some old patches up to date, see https://www.redhat.com/archives/libvir-list/2014-March/msg00106.html), I get the error:
getopt.h:85:29: fatal error: getopt-pfx-core.h: No such file or directory
when I run make (after running ./autogen.sh).
This is on libvirt commit aa50a5c.
In searching for this error ("fatal error: getopt-pfx-core.h: No such file or directory") I find very few results, but it does not seem specific to libvirt, which makes sense since the error seems to be something with getopt.
compiling libvirt
closed as off-topic by Jeff Schaller, phk, Michael Homer, G-Man, sebasth Jan 22 at 7:43
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions describing a problem that can't be reproduced and seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers." â Jeff Schaller, phk, Michael Homer, G-Man, sebasth
add a comment |Â
up vote
-1
down vote
favorite
up vote
-1
down vote
favorite
In trying to compile an old version of libvirt (to see if I can get some old patches up to date, see https://www.redhat.com/archives/libvir-list/2014-March/msg00106.html), I get the error:
getopt.h:85:29: fatal error: getopt-pfx-core.h: No such file or directory
when I run make (after running ./autogen.sh).
This is on libvirt commit aa50a5c.
In searching for this error ("fatal error: getopt-pfx-core.h: No such file or directory") I find very few results, but it does not seem specific to libvirt, which makes sense since the error seems to be something with getopt.
compiling libvirt
In trying to compile an old version of libvirt (to see if I can get some old patches up to date, see https://www.redhat.com/archives/libvir-list/2014-March/msg00106.html), I get the error:
getopt.h:85:29: fatal error: getopt-pfx-core.h: No such file or directory
when I run make (after running ./autogen.sh).
This is on libvirt commit aa50a5c.
In searching for this error ("fatal error: getopt-pfx-core.h: No such file or directory") I find very few results, but it does not seem specific to libvirt, which makes sense since the error seems to be something with getopt.
compiling libvirt
edited Jan 22 at 18:15
asked Jan 15 at 0:46
Azendale
3412514
3412514
closed as off-topic by Jeff Schaller, phk, Michael Homer, G-Man, sebasth Jan 22 at 7:43
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions describing a problem that can't be reproduced and seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers." â Jeff Schaller, phk, Michael Homer, G-Man, sebasth
closed as off-topic by Jeff Schaller, phk, Michael Homer, G-Man, sebasth Jan 22 at 7:43
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions describing a problem that can't be reproduced and seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers." â Jeff Schaller, phk, Michael Homer, G-Man, sebasth
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
0
down vote
accepted
Make sure that you are building with a clean tree.
In this case, I had files from a build of a much newer commit.
Running:
(warning, this deletes stuff in the working tree that is not in git!)
git reset --hard HEAD
git clean -fdx
git clean -fdX
and then doing the build again worked.
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
accepted
Make sure that you are building with a clean tree.
In this case, I had files from a build of a much newer commit.
Running:
(warning, this deletes stuff in the working tree that is not in git!)
git reset --hard HEAD
git clean -fdx
git clean -fdX
and then doing the build again worked.
add a comment |Â
up vote
0
down vote
accepted
Make sure that you are building with a clean tree.
In this case, I had files from a build of a much newer commit.
Running:
(warning, this deletes stuff in the working tree that is not in git!)
git reset --hard HEAD
git clean -fdx
git clean -fdX
and then doing the build again worked.
add a comment |Â
up vote
0
down vote
accepted
up vote
0
down vote
accepted
Make sure that you are building with a clean tree.
In this case, I had files from a build of a much newer commit.
Running:
(warning, this deletes stuff in the working tree that is not in git!)
git reset --hard HEAD
git clean -fdx
git clean -fdX
and then doing the build again worked.
Make sure that you are building with a clean tree.
In this case, I had files from a build of a much newer commit.
Running:
(warning, this deletes stuff in the working tree that is not in git!)
git reset --hard HEAD
git clean -fdx
git clean -fdX
and then doing the build again worked.
edited Jan 21 at 17:40
Jeff Schaller
31.8k848109
31.8k848109
answered Jan 15 at 0:48
Azendale
3412514
3412514
add a comment |Â
add a comment |Â