On Wed, Jun 10, 2015 at 9:56 PM, Eric Rubin-Smith wrote:
> -LIB = -m32 -L1/lib -lssl -lcrypto -lz -ldl -lm
> +LIB = -m32 -L1/lib /usr/lib/i386-linux-gnu/libssl.a
> /usr/lib/i386-linux-gnu/libcrypto.a -lz -ldl -lm
>
I suppose this is sexier:
LIB = -m32 -L1/lib -Wl,-static -lssl -lcrypto -Wl
On Wed, Jun 10, 2015 at 8:50 PM, Eric Rubin-Smith wrote:
>
>
> Eric: Can you discover what apt-get is needed in order to statically
>> link libssl using -m32?
>>
>
> Perhaps this?
>
> # apt-get install libssl-dev:i386
>
> Warning: I just got that command line from google and verified apt-get
> a
> Eric: Can you discover what apt-get is needed in order to statically
> link libssl using -m32?
>
Perhaps this?
# apt-get install libssl-dev:i386
Warning: I just got that command line from google and verified apt-get
accepted it -- didn't actually try to link against the libs in that package.
So... what do these 0-byte blobs _mean_ ?
I just took the time and rebuilt the repo and retried a pull, but same
problem (content does not match sha1 hash). Does anybody know what a
next step ought to be ?
-bch
On 6/8/15, bch wrote:
> rid: size
> ==
>
> 1355: 0
> 2090601: 0
> 2090613: 0
>
On 6/10/15, Richard Hipp wrote:
> On 6/10/15, Eric Rubin-Smith wrote:
>>
>> I believe you should be able to say:
>>
>> # apt-get install libssl-dev
>>
>
> That seemed to work. Thanks. I can now do the build with
> "./configure --static --disable-lineedit". (The --disable-lineedit
> was necessa
On Jun 10, 2015, at 1:46 PM, Richard Hipp wrote:
>
> Seems like somebody said that there are issues
> with openssl that prevent it from being statically linked.
I don’t know about that, but the last few times I’ve built Fossil on a
freshly-installed system sans libssl, the configure script erro
On 6/10/15, Eric Rubin-Smith wrote:
>
> I believe you should be able to say:
>
> # apt-get install libssl-dev
>
That seemed to work. Thanks. I can now do the build with
"./configure --static --disable-lineedit". (The --disable-lineedit
was necessary because apparently only the GNU readline pac
On Wed, Jun 10, 2015 at 3:46 PM, Richard Hipp wrote:
> On 6/10/15, Eric Rubin-Smith wrote:
> > On Wed, Jun 10, 2015 at 3:30 PM, Richard Hipp wrote:
> >
> >> On 6/10/15, Eric Rubin-Smith wrote:
> >> >
> >> > If you are worried that some people don't want the bloat of openssl in
> >> > their bas
On 6/10/15, Eric Rubin-Smith wrote:
> On Wed, Jun 10, 2015 at 3:30 PM, Richard Hipp wrote:
>
>> On 6/10/15, Eric Rubin-Smith wrote:
>> >
>> > If you are worried that some people don't want the bloat of openssl in
>> > their base fossil, perhaps provide both options on the site?
>> >
>>
>> It's n
On Wed, Jun 10, 2015 at 3:30 PM, Richard Hipp wrote:
> On 6/10/15, Eric Rubin-Smith wrote:
> >
> > If you are worried that some people don't want the bloat of openssl in
> > their base fossil, perhaps provide both options on the site?
> >
>
> It's not a question of bloat, its a question of wheth
On 6/10/15, Eric Rubin-Smith wrote:
>
> If you are worried that some people don't want the bloat of openssl in
> their base fossil, perhaps provide both options on the site?
>
It's not a question of bloat, its a question of whether or not we
require the user to have previously done "apt-get insta
$ fossil pull
Pull from https://eas@<...>/
HTTPS: Fossil has been compiled without SSL support
Pull done, sent: 0 received: 0 ip:
$
This burdens adoption, since now I have to build my own fossil and
distribute that to people on my team internally, rather than just pointing
them at the web site.
12 matches
Mail list logo
