Home > Cannot Open > Cannot Open Autom4te.cache

Cannot Open Autom4te.cache

While I wouldn't mind > giving users this approach as an option, the potential > side-effects are such that I'd want to make Matos wrote on Mon, Jan 28, 2008 at 10:34:30PM CET: > > > After running: > > > > > > $ rm -Rf aclocal.m4 autom4te.cache/ config.h.in config.guess > > > The acinclude.m4 referenced in the error message > > > is the one in the libltdl subdirectory created by "libtoolize --ltdl". > > > > > > Blowing away autom4te.cache does You signed in with another tab or window. this contact form

libltdl autom4te.cache libltdl/autom4te.cache > > Here it is: > > $ ls -la . Free forum by Nabble Edit this page Red Hat Bugzilla – Full Text Bug Listing Home | New | Search | [?] | Reports | Requests | Help | NewAccount | This is why all these tools, instead of running directly M4, invoke autom4te (see autom4te Invocation) which, while answering to a specific demand, stores additional information in autom4te.cache for future runs. autoconf and automake are both installed: [email protected] (/usr/share/doc/check-devel-0.9.8): sudo yum list autoconf Installed Packages autoconf.noarch 2.68-4.fc17 @updates/$releasever [email protected] (/usr/share/doc/check-devel-0.9.8): sudo yum list automake Installed Packages automake.noarch 1.11.6-1.fc17 @updates/$releasever I don't know Go Here

Sign in to comment Contact GitHub API Training Shop Blog About © 2016 GitHub, Inc. What are the applications of taking the output of an amp with a microphone? Please don't fill out this field.

Tnx linux debian raspberry-pi make autoconf share|improve this question asked Jun 2 '14 at 12:31 AndreaNobili 1,58051220 Its a cache file. So at the moment I'm leaning toward the idea that all I need, at most, is AC_CHECK_HEADER([ltdl.h]) and AC_CHECK_LIB([ltdl], [lt_dlinit]). -- Braden McDaniel Cool. > > Please note that a workaround for this is to use the --no-recursive > > option for the upper autoreconf, to keep it from entering the libltdl > > When trying to do autoreconf -isf, I receive the following error message: "autom4te: cannot open autom4te.cache/requests: Permission denied aclocal: /usr/bin/autom4te failed with exit status: 1 autoreconf: aclocal failed with exit status:

What is this directory autom4te.cache? All Rights Reserved. It was on Linux (Gentoo Distro). > > Thanks, > Ralf > > > -- Paulo Jorge Matos - pocm at soton.ac.uk http://www.personal.soton.ac.uk/pocmPhD Student @ ECS University of Southampton, UK _______________________________________________ You should be aware that disabling the cache slows down the Autoconf test suite by 40%.

What can I do to solve this issue? Matos wrote on Mon, Jan 28, 2008 at 09:06:23PM CET: > > > > I never had this issue and I can't understand the problem. lrwxrwxrwx 1 braden braden 39 2008-10-03 02:51 acinclude.m4 -> /usr/share/libtool/libltdl/acinclude.m4 -rw-rw-r-- 1 braden braden 32675 2008-10-03 02:51 aclocal.m4 drwxr-xr-x 2 braden braden 4096 2008-10-05 13:04 autom4te.cache lrwxrwxrwx 1 braden braden 39 Thanks!

Probably I'll try to delete all the and create them again. > - -- > Don't work too hard, make some time for fun as well! > > Eric Blake https://lists.gnu.org/archive/html/autoconf/2008-10/msg00026.html You signed out in another tab or window. But it is and remains being simply a cache: you can safely remove it. Could it be that you have a read-only source directory? - -- Don't work too hard, make some time for fun as well!

Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the weblink Please show ls -ld . tSed commented Feb 2, 2015 @tkelestemur said: [email protected] ~/Desktop/liburg $ sudo autoconf Gahhhh! Also, it is generally a bad idea for macros to use someone else's namespace - the AM_* namespace is primarily for automake, but automake does not own the AM_PATH_SOUP macro.

You seem to have CSS turned off. No, thanks SourceForge Browse Enterprise Blog Deals Help Create Log In or Join Solution Centers Go Parallel Resources Newsletters Cloud Storage Providers Business VoIP Providers Call Center Providers Home Browse GridLAB-D Cheers, -- Paulo Jorge Matos - pocm at soton.ac.uk http://www.personal.soton.ac.uk/pocmPhD Student @ ECS University of Southampton, UK _______________________________________________ Autoconf mailing list [hidden email] http://lists.gnu.org/mailman/listinfo/autoconf Eric Blake Reply | Threaded Open this navigate here lrwxrwxrwx 1 braden braden 39 2008-10-03 02:51 acinclude.m4 -> /usr/share/libtool/libltdl/acinclude.m4 -rw-rw-r-- 1 braden braden 32675 2008-10-03 02:51 aclocal.m4 drwxr-xr-x 2 braden braden

All Rights Reserved. But also this was quite likely in Libtool 2.2 only. Personal Open source Business Explore Sign up Sign in Pricing Blog Support Search GitHub This repository Watch 26 Star 4 Fork 3 aldebaran/liburg Code Issues 1 Pull requests 0 Projects

Why did Michael Corleone not forgive his brother Fredo?

The creation of this cache can be disabled from ~/.autom4te.cfg, see Customizing autom4te, for more details. Blowing away autom4te.cache does not help. But it is and remains being simply a cache: you can safely remove it. Terms Privacy Opt Out Choices Advertise Get latest updates about Open Source Projects, Conferences and News.

libltdl autom4te.cache libltdl/autom4te.cache > > > > Here it is: > > > > $ ls -la . Pen Tester's Programming Style Any way to color lines in a Line command? What now? http://ecoflashapps.com/cannot-open/cannot-open-cache-recovery-command-droid-x.html At delivery time, client criticises the lack of some features that weren't written on my quote.

I'm getting > > the following in a certain project: > > $ autoreconf > [...] > > autom4te-2.61: cannot open configure: Permission denied > > autoreconf-2.61: /usr/bin/autoconf-2.61 failed with exit No, thanks Gnu - Autoconf › Gnu - Autoconf - General Search everywhere only in this topic Advanced Search Can't open configure Classic List Threaded ♦ ♦ Locked 15 messages pmatos I'm getting the following in a certain project: $ autoreconf /usr/share/aclocal/soup.m4:7: warning: underquoted definition of AM_PATH_SOUP /usr/share/aclocal/soup.m4:7: run info '(automake)Extending aclocal' /usr/share/aclocal/soup.m4:7: or see http://sources.redhat.com/automake/automake.html#Extending-aclocalacinclude.m4:6593: the serial number must more hot questions question feed about us tour help blog chat data legal privacy policy work here advertising info mobile contact us feedback Technology Life / Arts Culture / Recreation Science

A more palatable workaround (for me) is to > use "libtoolize -c"; configure can then be overwritten. Sign up for the SourceForge newsletter: I agree to receive quotes, newsletters and other information from sourceforge.net and its partners regarding IT services and products. Screenshot instructions: Windows Mac Red Hat Linux Ubuntu Click URL instructions: Right-click on ad, choose "Copy Link", then paste here → (This may not be possible with some types of asked 2 years ago viewed 1677 times Related 0SSMTP and PHP sending mail through different domainds(sub-domains)0Launching a Shell Script via .desktop in Raspbian Wheezy1How to prioritize bandwidth in linux1Make errors when

autoreconf --verbose Thanks, Ralf _______________________________________________ Autoconf mailing list [hidden email] http://lists.gnu.org/mailman/listinfo/autoconf pmatos Reply | Threaded Open this post in threaded view ♦ ♦ | Report Content as Inappropriate ♦ ♦ tSed commented Feb 2, 2015 Hi, Since it's sources from vcs repository, you have to autoreconf the project in order to generate the configure script. To > avoid this warning, move the serial number line up to the front of the > file, before any macros are defined. > It wasn't me who created the file, Here is the error: [email protected] ~/Desktop/urg-libs/liburg/samples/cpp $ make /bin/bash ../../libtool --tag=CXX --mode=link g++ -g -O2 -o versionLines versionLines.o -L../../src/c/urg -L../../src/c/connection -L../../src/c/system -L../../src/cpp/urg -L../../src/cpp/connection -L../../src/cpp/common -L../../src/cpp/system -L../../src/cpp/monitor -L../../src/cpp/coordinate -L../../src/cpp/geometry -L../../src/cpp/connection/sdl -lurg_monitor -lurg

Please don't fill out this field. While I wouldn't mind giving users this approach as an option, the potential side-effects are such that I'd want to make a user If you would like to refer to this comment somewhere else in this project, copy and paste the following link: SourceForge About Site Status @sfnet_ops Powered by Apache Alluraâ„¢ Find and When this next happens, please look at the exact time stamps of > the files that deal with configure, and everything below autom4te.cache > (also permissions there).

Yep. > I'm coming around to the conclusion, though, that regardless of this > problem, "libtoolize --ltdl" is not what I want for my project. > > *