Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] missing reference to libm for MicroPerl
Date: Thu, 08 Mar 2012 00:07:06 +0100	[thread overview]
Message-ID: <87vcmgdn8l.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <CADxd2g8k8X=xNBWdE=dSbCUnkupecS1LdDZwiVYKiYTry1Uo4A@mail.gmail.com> (Joshua Jackson's message of "Tue, 6 Mar 2012 11:46:06 -0500")

>>>>> "Joshua" == Joshua Jackson <jjackson@vortech.net> writes:

 Joshua> I am currently running into an issue with the compilation of MicroPerl
 Joshua> fails with a missing libm reference. I found the following patch that
 Joshua> was date from a couple years ago:

 Joshua> This fixes builds on my system, but I'm not sure what else it
 Joshua> might break.

 Joshua> Is there another fix / setting I might be missing to prevent
 Joshua> the need for this patch?

Thanks. I committed a similar patch to git from Arnout earlier this
week.

-- 
Bye, Peter Korsgaard

      reply	other threads:[~2012-03-07 23:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-06 16:46 [Buildroot] missing reference to libm for MicroPerl Joshua Jackson
2012-03-07 23:07 ` Peter Korsgaard [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87vcmgdn8l.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox