| 2012-12-26 09:44:06 |
i30817 |
bug |
|
|
added bug |
| 2012-12-26 13:48:10 |
William Grant |
launchpad: status |
New |
Invalid |
|
| 2012-12-26 15:28:41 |
i30817 |
launchpad: status |
Invalid |
New |
|
| 2012-12-26 16:21:08 |
todaioan |
launchpad: status |
New |
Fix Committed |
|
| 2012-12-26 16:21:08 |
todaioan |
launchpad: assignee |
|
todaioan (alan-ar06) |
|
| 2012-12-26 16:33:43 |
todaioan |
removed subscriber todaioan |
|
|
|
| 2012-12-26 16:34:10 |
todaioan |
bug |
|
|
added subscriber todaioan |
| 2012-12-26 16:34:13 |
todaioan |
removed subscriber todaioan |
|
|
|
| 2012-12-26 16:34:16 |
todaioan |
bug |
|
|
added subscriber todaioan |
| 2012-12-26 16:34:19 |
todaioan |
removed subscriber todaioan |
|
|
|
| 2012-12-26 17:12:25 |
Micah Gersten |
launchpad: status |
Fix Committed |
Invalid |
|
| 2012-12-26 17:12:25 |
Micah Gersten |
launchpad: assignee |
todaioan (alan-ar06) |
|
|
| 2012-12-27 22:21:38 |
i30817 |
launchpad: status |
Invalid |
New |
|
| 2012-12-28 11:52:33 |
William Grant |
launchpad: status |
New |
Invalid |
|
| 2012-12-28 12:31:49 |
i30817 |
description |
For static dependencies of course.
Currently it fails by either 'no tty and no askpass program specified' or 'permission denied' if not using sudo. The workaround is changing the makefile to not use the system library but a relative path to it (without install) and copying the headers to a place the makefile finds or adding that too to the makefile.
Very ugly workaround, and gives not allowing the install additional advantage afaik, since the build env is temporary. |
Edit: for googlers trying to make this: the whole discussion was predicated on a false assumption (that there was no way to add a debian package dependency not on the official packages). In fact, there is: send your dependencies builds to the 'main' ppa of the recipe. So the way to success is using a debian packaging still)
For static dependencies of course.
Currently it fails by either 'no tty and no askpass program specified' or 'permission denied' if not using sudo. The workaround is changing the makefile to not use the system library but a relative path to it (without install) and copying the headers to a place the makefile finds or adding that too to the makefile.
Very ugly workaround, and gives not allowing the install additional advantage afaik, since the build env is temporary. |
|
| 2012-12-28 12:31:57 |
i30817 |
description |
Edit: for googlers trying to make this: the whole discussion was predicated on a false assumption (that there was no way to add a debian package dependency not on the official packages). In fact, there is: send your dependencies builds to the 'main' ppa of the recipe. So the way to success is using a debian packaging still)
For static dependencies of course.
Currently it fails by either 'no tty and no askpass program specified' or 'permission denied' if not using sudo. The workaround is changing the makefile to not use the system library but a relative path to it (without install) and copying the headers to a place the makefile finds or adding that too to the makefile.
Very ugly workaround, and gives not allowing the install additional advantage afaik, since the build env is temporary. |
Edit: for googlers trying to make this: the whole discussion was predicated on a false assumption (that there was no way to add a debian package dependency not on the official packages). In fact, there is: send your dependencies builds to the 'main' ppa of the recipe. So the way to success is using a debian packaging still)
For static dependencies of course.
Currently it fails by either 'no tty and no askpass program specified' or 'permission denied' if not using sudo. The workaround is changing the makefile to not use the system library but a relative path to it (without install) and copying the headers to a place the makefile finds or adding that too to the makefile.
Very ugly workaround, and gives not allowing the install additional advantage afaik, since the build env is temporary. |
|
| 2012-12-28 12:32:07 |
i30817 |
description |
Edit: for googlers trying to make this: the whole discussion was predicated on a false assumption (that there was no way to add a debian package dependency not on the official packages). In fact, there is: send your dependencies builds to the 'main' ppa of the recipe. So the way to success is using a debian packaging still)
For static dependencies of course.
Currently it fails by either 'no tty and no askpass program specified' or 'permission denied' if not using sudo. The workaround is changing the makefile to not use the system library but a relative path to it (without install) and copying the headers to a place the makefile finds or adding that too to the makefile.
Very ugly workaround, and gives not allowing the install additional advantage afaik, since the build env is temporary. |
Edit: for googlers trying to make this: the whole discussion was predicated on a false assumption (that there was no way to add a debian package dependency not on the official packages). In fact, there is: send your dependencies builds to the 'main' ppa of the recipe. So the way to success is using a debian packaging still)
For static dependencies of course.
Currently it fails by either 'no tty and no askpass program specified' or 'permission denied' if not using sudo. The workaround is changing the makefile to not use the system library but a relative path to it (without install) and copying the headers to a place the makefile finds or adding that too to the makefile.
Very ugly workaround, and gives not allowing the install additional advantage afaik, since the build env is temporary. |
|
