Home > Failed With > Autom4te Failed With Exit Status 137

Autom4te Failed With Exit Status 137

Contents

You signed out in another tab or window. Note You need to log in before you can comment on or make changes to this bug. the only thing we have is a load/suspended theshold in the grid it self. (np_load_av, 1.75) at if I give it the memory limit I get the same result but the http://ftp.mozilla.org/pub/mozilla/nightly/latest-trunk/mozilla-source.tar.bz2 Comment 3 Martin Mokrejs 2003-01-09 07:05:18 PST Yes, I've downloaded the nighly snapshot from the suggest URL and it is still in there: [...] checking for xargs... /software/@sys/usr/bin/xargs checking for have a peek here

Sign in to comment Contact GitHub API Training Shop Blog About © 2017 GitHub, Inc. Comment 2 Olivier Cahagne 2003-01-09 04:01:15 PST got e-mail from reporter: this is with release 1.0.2. We recommend upgrading to the latest Safari, Google Chrome, or Firefox. If you have further comments please address them to [email protected], and the maintainer will reopen the bug report if appropriate.

Aclocal: Error: Echo Failed With Exit Status: 1

Message #5 received at [email protected] (full text, mbox, reply): From: Daniel Schepler To: [email protected] Subject: util-linux: FTBFS: m4 runs out of memory Date: Sun, 22 Sep 2013 17:39:27 -0700 Source: javiercr commented Oct 11, 2016 I had the same issue with kubernetes v1.4.0, a pod crashed with ExitCode 137 but no indication of OOM. cc checking whether the C compiler (cc -O2 -arch ev56 ) works... Reload to refresh your session.

You signed in with another tab or window. After executing 'sh autogen.sh' it takes quite a while, then the following messages appear: Killed autom4te: /usr/bin/m4 failed with exit status: 137 aclocal: /usr/bin/autom4te failed with exit status: 137 autoreconf: aclocal Changing to previous m4 version (m4_1.4.16-5_amd64.deb) makes no difference: The commands being run are: /usr/bin/sh autopoint --force which runs: /usr/bin/perl -w /usr/bin/autom4te --no-cache --language=Autoconf-without-aclocal-m4 --trace=AM_GNU_GETTEXT_VERSION:$% - configure.ac which runs: sh -c Contributor gpakosz commented Mar 2, 2012 well that's where I started, I first installed autoconf from homebrew-alt.

Looks like it's to late to prevent kicking it out of the system. > > > > What about using s_vmem then? Otherwise necessary cleanups couldn't be executed. > > > > > > I see this. Also, I don't have to run autoconf/automake to regenerate configure in the case of snapshots, and it is still present! $ ./configure --enable-crypto --with-libIDL-prefix=/software/@sys/usr creating cache ./config.cache checking host system type... https://groups.google.com/d/topic/security-onion/Yb4NM8KPmw4 It breaks while trying to compile the "nl-pktloc-lookup" >>>>>>>> binary.

Are there any plans to merge the DECT changes upstream? >>>>>> >>>>>> Cheers, >>>>>> Stephan > Previous message: Compile of libnl failed Next message: Compile of libnl failed Messages sorted by: While previous versions of libnl compiled fine on the same machine. > > 28.06.2013, 15:32, "Stephan Meier" : >> Hi, >> >> not really. Reply sent to Helmut Grohne : You have taken responsibility. (Sat, 25 Jan 2014 19:21:18 GMT) Full text and rfc822 format available. cxx -E checking for a BSD compatible install... /software/@sys/usr/bin/install -c checking whether ln -s works...

Autom4te: /usr/bin/m4 Failed With Exit Status: 1

Comment 10 Tracy Walker [:tracy] 2003-02-05 12:45:19 PST Martin, please reopen if this still exists. I need them to build software projects of mine and never encountered any clash with Macports masking Apple's stock binaries (although I understand your mileage may vary). Aclocal: Error: Echo Failed With Exit Status: 1 configure.ac:45: the top level autom4te: /usr/bin/m4 failed with exit status: 63 aclocal: /usr/local/Cellar/autoconf/2.68/bin/autom4te failed with exit status: 63 autoreconf: aclocal failed with exit status: 63 offending line: /usr/share/aclocal/libtool.m4:51: LT_PREREQ is expanded Acknowledgement sent to Daniel Schepler : New Bug report received and forwarded.

Contributor ApsOps commented Oct 11, 2016 I think this could happen when a container liveness probe fails. @javiercr could you check if this was the case for you? http://smartnewsolutions.com/failed-with/method-lib-svc-method-fs-local-failed-with-exit-status-95.html no checking for perl... /software/@sys/usr/bin/perl checking for minimum required perl version >= 5.004... 5.008 checking for full perl installation... But that's ok I love Homebrew so much I don't mind raping my /usr/share/aclocal folder :) Also, I understand people who moved to Lion and Xcode 4.3 already don't face the Copy sent to LaMont Jones . (Mon, 23 Sep 2013 00:42:11 GMT) Full text and rfc822 format available.

I get exactly the same issue building this package in current amd64 unstable chroot. > > Changing to previous m4 version (m4_1.4.16-5_amd64.deb) makes no difference: > > The commands being run no checking for make... /software/@sys/usr/bin/make checking whether /software/@sys/usr/bin/make sets ${MAKE}... ./configure: bad substitution $ aclocal aclocal: configure.in: 2522: macro `AM_PATH_NSPR' not found in library aclocal: configure.in: 2834: macro `AM_PATH_GTK' not found Helmut Grohne (supplier of updated util-linux package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators Check This Out I get exactly the same issue building this package in current amd64 unstable chroot.

Contributor ApsOps commented Oct 11, 2016 @javiercr Have you setup a LivenessProbe in your pod config? We recommend upgrading to the latest Safari, Google Chrome, or Firefox. Already have an account?

Send a report that this bug log contains spam.

A single word for "the space in between" Would more Full Nodes help scaling and transaction speed? I've found that exactly same code works for example in configure under gimp-1.2.4-rc2: $2= checking whether make sets ${MAKE}... $ac_make=make $ac_cv_prog_make_make_set=make_set yes Comment 8 hacker formerly known as seawood@netscape.com 2003-01-31 15:41:09 Member mxcl commented Mar 6, 2012 Worth noting on a fresh Lion install, installing just Xcode 4.3, the offending libtool.m4 does not exist. Debian bug tracking system administrator .

Notification sent to Daniel Schepler : Bug acknowledged by developer. (Sat, 25 Jan 2014 19:21:19 GMT) Full text and rfc822 format available. The epilog will be executed, but not the remainder of the job script. The job will get a signal SIGXCPU and can act upon like using a trap in the jobscript. this contact form configure.in: required file `./install-sh' not found configure.in: required file `./mkinstalldirs' not found configure.in: required file `./missing' not found automake: no `Makefile.am' found or specified $ autoconf build/autoconf/altoptions.m4:140: error: m4_defn: undefined macro:

Does someone have a clue why? Contributor therc commented Feb 1, 2016 Maybe it's upstream: docker/docker#18510 Contributor ApsOps commented Jul 19, 2016 • edited I'm facing the same issue here. Join them; it only takes a minute: Sign up Error with aclocal up vote 0 down vote favorite I have an error while trying to run aclocal although i have the Contributor gpakosz commented Mar 2, 2012 Is it worth trying to fix it?

or how to catch it? > > > > > > > > > > > > Lars > > > > > > > > > > > > _______________________________________________ Please re-read the detailed build instructions at http://www.mozilla.org/build/unix-details.html . I suspect it has to do with the `@' sign, actually `@sys'.