Hello,
I am trying to compile a program that there is no RPM for. I hope to use this experience to learn how to make RPM's as well.
I am starting to use Atmel AVR's and I want to try this program. http://savannah.nongnu.org/projects/simulavr/
(The latest tar file is dated 2008-03-16) http://download.savannah.nongnu.org/releases/simulavr/
I am looking at other options as well.
While trying to compile the program, I have installed most of the devel and libs so I only get three or four error messages when running ./configure
One of them that I cannot find any answers to is where do I find ac_nonexitent.h. I have searched Google (31,800 hits) and I see that this is a common question for many users but I never see an answer. Two days of looking and I am no closer to an answer. I did solve the issue with vfork.h (use unistd.h) this morning. :)
As others have asked in my searches, I have errors when compiling and trying to fix all the ./configure issues first.
Is there someone on this list that can at least point me in the right direction on this question, even to what this header is supposed to do?
I have either F7 or F8 to work with.
Robin Laing wrote:
I am trying to compile a program that there is no RPM for. I hope to use this experience to learn how to make RPM's as well.
:)
I am starting to use Atmel AVR's and I want to try this program. http://savannah.nongnu.org/projects/simulavr/
(The latest tar file is dated 2008-03-16) http://download.savannah.nongnu.org/releases/simulavr/
I am looking at other options as well.
While trying to compile the program, I have installed most of the devel and libs so I only get three or four error messages when running ./configure
One of them that I cannot find any answers to is where do I find ac_nonexitent.h. I have searched Google (31,800 hits) and I see
^ an 's' is missing, isn't it?
that this is a common question for many users but I never see an answer. Two days of looking and I am no closer to an answer. I did solve the issue with vfork.h (use unistd.h) this morning. :)
As others have asked in my searches, I have errors when compiling and trying to fix all the ./configure issues first.
Does configure exit cleanly or does it throw an error when this happens? I *think* that ac_nonexistent.h is something autoconf uses to test and isn't supposed to exist. (But I've not found that documented ATM.) I can tell you that a similar message is found in the config.log of some software I successfully build all the time.
What errors are you getting from make? It might be worth posting a link to the output from ./configure && make (and perhaps also the config.log file).
Todd Zullinger wrote:
Robin Laing wrote:
I am trying to compile a program that there is no RPM for. I hope to use this experience to learn how to make RPM's as well.
:)
I am starting to use Atmel AVR's and I want to try this program. http://savannah.nongnu.org/projects/simulavr/
(The latest tar file is dated 2008-03-16) http://download.savannah.nongnu.org/releases/simulavr/
I am looking at other options as well.
While trying to compile the program, I have installed most of the devel and libs so I only get three or four error messages when running ./configure
One of them that I cannot find any answers to is where do I find ac_nonexitent.h. I have searched Google (31,800 hits) and I see
^ an 's' is missing, isn't it?
that this is a common question for many users but I never see an answer. Two days of looking and I am no closer to an answer. I did solve the issue with vfork.h (use unistd.h) this morning. :)
As others have asked in my searches, I have errors when compiling and trying to fix all the ./configure issues first.
Does configure exit cleanly or does it throw an error when this happens? I *think* that ac_nonexistent.h is something autoconf uses to test and isn't supposed to exist. (But I've not found that documented ATM.) I can tell you that a similar message is found in the config.log of some software I successfully build all the time.
What errors are you getting from make? It might be worth posting a link to the output from ./configure && make (and perhaps also the config.log file).
I am doing this at home so I cannot remember the last error message. I spent most of last night getting rid of all but four error messages in the config.log file. I was missing many headers at first as well as other things like bison and yacc. Some simple things as well.
The last two times I tried to run, it stopped with error messages but that was before I got rid of even more missing items in the log.
Hopefully tonight I will be able to get an answer. I am expecting an error related to vfork as it is may be looking for the wrong header. I will have to check the config file (another new experience). :)
Robin Laing wrote:
Todd Zullinger wrote:
Robin Laing wrote:
I am doing this at home so I cannot remember the last error message. I spent most of last night getting rid of all but four error messages in the config.log file. I was missing many headers at first as well as other things like bison and yacc. Some simple things as well.
The last two times I tried to run, it stopped with error messages but that was before I got rid of even more missing items in the log.
Hopefully tonight I will be able to get an answer. I am expecting an error related to vfork as it is may be looking for the wrong header. I will have to check the config file (another new experience). :)
While it compiled after some finger problems and ran okay. I didn't fix the vfork warning. Now to start looking at making rpm's.
It would be nice to find out a definitive answer on ac_nonexitent.h though. Seeing many, many posts on this error with no definitive answer is an issue. What list/forum would be a good place to ask?
Robin Laing wrote:
While it compiled after some finger problems and ran okay. I didn't fix the vfork warning. Now to start looking at making rpm's.
Cool. Post back if you have questions on that part. If you haven't got better links, there's a draft on the fedoraproject.org wiki for building packages:
http://fedoraproject.org/wiki/Docs/Drafts/BuildingPackagesGuide
I can't say I've followed it to learn to package (since it was created long after I'd struggled to learn to build rpms :), but it does seem to cover many of the things you'll need to know.
It would be nice to find out a definitive answer on ac_nonexitent.h though. Seeing many, many posts on this error with no definitive answer is an issue. What list/forum would be a good place to ask?
I looked harder and this is definitely an autoconf test. The purpose it to determine whether the preprocessor can detect missing headers. You can find it in /usr/share/autoconf/autoconf/c.m4:
# OK, works on sane cases. Now check whether nonexistent headers # can be detected and how. _AC_PREPROC_IFELSE([AC_LANG_SOURCE([[@%:@include <ac_nonexistent.h>]])], [# Broken: success on invalid input. continue], [# Passes both tests. ac_preproc_ok=:
No need to really worry about it. If it shows up in the configure output, perhaps that could be fixed in the upstream configure.ac (or configure.in), but it's not an error that should affect the build AFAICT.
Todd Zullinger wrote:
Robin Laing wrote:
While it compiled after some finger problems and ran okay. I didn't fix the vfork warning. Now to start looking at making rpm's.
Cool. Post back if you have questions on that part. If you haven't got better links, there's a draft on the fedoraproject.org wiki for building packages:
http://fedoraproject.org/wiki/Docs/Drafts/BuildingPackagesGuide
I have many building rpm links/howto's to start with but it never hurts to have more from time to time.
In the past I just used CheckInstall but that seems to have dropped off in support.
I can't say I've followed it to learn to package (since it was created long after I'd struggled to learn to build rpms :), but it does seem to cover many of the things you'll need to know.
It would be nice to find out a definitive answer on ac_nonexitent.h though. Seeing many, many posts on this error with no definitive answer is an issue. What list/forum would be a good place to ask?
I looked harder and this is definitely an autoconf test. The purpose it to determine whether the preprocessor can detect missing headers. You can find it in /usr/share/autoconf/autoconf/c.m4:
# OK, works on sane cases. Now check whether nonexistent headers # can be detected and how. _AC_PREPROC_IFELSE([AC_LANG_SOURCE([[@%:@include <ac_nonexistent.h>]])], [# Broken: success on invalid input. continue], [# Passes both tests. ac_preproc_ok=:
No need to really worry about it. If it shows up in the configure output, perhaps that could be fixed in the upstream configure.ac (or configure.in), but it's not an error that should affect the build AFAICT.
Now this is nice to know. I will read some more and learn more.
It has been a fun week so far in learning about the different programming tools. Trying to get my old mind back into C programming that I learned before there was a Netscape or PPP access in our city. Heck, we didn't even have an ISP. :)
I am learning I have a lot more to learn. My AVR project is the highest priority and this is why I want to get a simulator that works. :)
Robin Laing wrote:
In the past I just used CheckInstall but that seems to have dropped off in support.
That's probably for the best. Using checkinstall requires you to do make install as root, right? That can be problematic unless you've tested make install as a normal user (using $DESTDIR or a $prefix you have write access to). The problem is that sometimes there are errors in upstream Makefiles or even in the options you might pass to configure. Running make install as root could accidentally overwrite existing (and critical) files on your system.
One of the most important things about building rpms, in my opinion, is to do the building as a normal user. This will help you catch such problems and then correct them -- before they bite you.
It has been a fun week so far in learning about the different programming tools. Trying to get my old mind back into C programming that I learned before there was a Netscape or PPP access in our city. Heck, we didn't even have an ISP. :)
I am learning I have a lot more to learn. My AVR project is the highest priority and this is why I want to get a simulator that works. :)
Happy hacking!