You'll need the link to the raw gist, which you can get by clicking the < > icon on your gist page. You'll probably want to drop the second ID out of the URL (the commit hash) so that the URL stays valid as you continue to make edits to the gist.
On Wed, Oct 9, 2013 at 10:42 PM, Robert Fletcher <[email protected]>wrote: > Okay, running this: > > anvil build > http://downloads.sourceforge.net/project/lpsolve/lpsolve/5.5.0.13/lp_solve_5.5.0.13_source.tar.gz-b > https://gist.github.com/mockdeep/6912134 > > Gets me this: > > Launching build process... done > Preparing app for compilation... done > Fetching buildpack... failed > Unknown buildpack type: https://gist.github.com/mockdeep/6912134 > Build Error: exited 1 > > > > On Wed, Oct 9, 2013 at 7:34 PM, Robert Fletcher <[email protected]>wrote: > >> Okay, progress made. I've got it compiled locally and pushed it up. I got >> the following exception on Heroku: >> >> ~ $ bin/lp_solve >> bin/lp_solve: /lib/libc.so.6: version `GLIBC_2.14' not found (required by >> bin/lp_solve) >> >> I'm assuming this means I just need to compile it on Heroku instead. This >> is where I'm getting caught up. In order to compile, all that needs to >> happen is to cd into `lp_solve_5.5/lp_solve/` and execute the script `ccc`, >> then grab the `lp_solve` file that is generated. So I guess the script >> would look something like this: https://gist.github.com/mockdeep/6912134 >> >> Does that look correct? How do I go about executing that with anvil? >> >> >> On Wed, Oct 9, 2013 at 6:27 PM, Daniel Farina <[email protected]> wrote: >> >>> >>> On Oct 9, 2013 6:25 PM, "Robert Fletcher" <[email protected]> >>> wrote: >>> > >>> > The file output on Heroku was the same as local: >>> > >>> > ~ $ file bin/lp_solve >>> > bin/lp_solve: ELF 32-bit LSB executable, Intel 80386, version 1 >>> (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.2.5, not >>> stripped >>> >>> Great, that means 'file' can be used to spot such problems. Thanks for >>> looking into that. >>> >>> -- >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Heroku" group. >>> >>> To unsubscribe from this group, send email to >>> [email protected] >>> For more options, visit this group at >>> http://groups.google.com/group/heroku?hl=en_US?hl=en >>> >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "Heroku Community" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >> >> > -- > -- > You received this message because you are subscribed to the Google > Groups "Heroku" group. > > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en_US?hl=en > > --- > You received this message because you are subscribed to the Google Groups > "Heroku Community" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > -- -- You received this message because you are subscribed to the Google Groups "Heroku" group. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups "Heroku Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
