Displaying 20 results from an estimated 10000 matches similar to: "[Bug 194] New: still problems with libutil"
2002 Apr 23
16
[Bug 194] still problems with libutil
http://bugzilla.mindrot.org/show_bug.cgi?id=194
------- Additional Comments From djm at mindrot.org 2002-04-23 23:29 -------
This should be fixed in -current CVS, please test
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
2003 Jan 01
0
[Bug 462] New: compile failure with openssl 0.9.7
http://bugzilla.mindrot.org/show_bug.cgi?id=462
Summary: compile failure with openssl 0.9.7
Product: Portable OpenSSH
Version: 3.5p1
Platform: ix86
OS/Version: Linux
Status: NEW
Severity: major
Priority: P2
Component: Build system
AssignedTo: openssh-unix-dev at mindrot.org
ReportedBy:
2001 Oct 31
1
OpenSSH-3.0p1-pre-CVS: configure.ac checks for login in -lutil and -lbsd?
OpenSSH-3.0p1-pre, from CVS as of about 2001-10-30 23:45 UTC.
Any particular reason why configure is checking for login() in -lutil,
finds it, then checks for it again in -lbsd?
Here's the relevant excerpts (Red Hat Linux 6.2, , kernel-2.2.19,
glibc-2.1.3, egcs-1.1.2, autoconf-2.52):
$ CFLAGS='-O2 -mpentium -Wall'; export CFLAGS
$ ./configure
2003 Jan 31
3
OpenSSH & OpenSSL directory location problem.
Problem: scp does not work with custom openssl library location
OpenSSH & OpenSSL directory location problem.
checking whether snprintf correctly terminates long strings... yes
checking whether getpgrp requires zero arguments... yes
checking OpenSSL header version... 90608f (OpenSSL 0.9.6h [engine] 5
Dec 2002)
checking OpenSSL library version... 90608f (OpenSSL 0.9.6h [engine] 5
Dec
2001 Feb 13
1
configure.in reorder patch
Feb 12 CVS (sort of, see warning below)
I've had to change around some of the code in configure.in
to get some platforms to compile with the --with-tcp-wrappers option.
Basicly I have set it up to
check headers
check system libraries
check for optional packages
check functions
I have also tried to clean up the library order as it is important
on some platforms.
This patch works on
Solaris
2019 Apr 02
0
Make/Build Error on armhf
Hi,
I noticed the same, actually with many more shared libraries. It already
has been filed as bug https://bugzilla.samba.org/show_bug.cgi?id=13754
with version 4.10.0rc4 .
Looking at what actually happens in detail no exotic build options are
used so at first sight it looks more like a problem of the build tools
on the RPi than a Samba problem.
The simplest situation I could find was
2005 Jan 12
1
Compiling openssh-3.9p1 Without Kerberos
I'm trying to compile openssh-3.9p1 for an embedded Linux distro without
kerberos support. I pass the flag --without-kerberos5 to configure and
the script output indicates that I've chosen to not link against the
kerberos libs:
OpenSSH has been configured with the following options:
User binaries: /usr/local/bin
System binaries: /usr/local/sbin
2019 Apr 04
0
Make/Build Error on armhf
I tried the backports tip from https://bugzilla.samba.org/show_bug.cgi?id=13754 and samba 4.10.1 this works... compile finishes without an error...
-----Ursprüngliche Nachricht-----
Von: samba <samba-bounces at lists.samba.org> Im Auftrag von Dirk Laurenz via samba
Gesendet: Dienstag, 2. April 2019 23:32
An: samba at lists.samba.org
Cc: 'Norbert Hanke' <norbert.hanke at
2004 Jan 11
1
cross compling openssh-3.5p1 for ppc
Greetings:
------------ BACKGROUND --------------------------
I am using the Monta Vista development kit on an Intel RedHat Linux
platform... the target is PPC_405.
The configure utility that comes with the openssh-3.5p1 code will not
support cross compilation. It gives an error message about not being able
to test its results and then exits before it creates a Makefile. To get
around this
2007 Jan 17
3
[Bug 1276] Link stage fails when gssapi exists
http://bugzilla.mindrot.org/show_bug.cgi?id=1276
Summary: Link stage fails when gssapi exists
Product: Portable OpenSSH
Version: v4.5p1
Platform: ix86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Build system
AssignedTo: bitbucket at mindrot.org
ReportedBy: jengelh
2000 Jul 08
1
sshd Pam problem for Redhat 6.2
Hi,
There was another message about this from Darren Evans. I am hoping that
the logs from below might shed additional light on this problem (kernel
version 2.2.14). I'm running Redhat 6.2, openssh-2.1.1p2.tar.gz,
openssl-0.9.5a.tar.gz.
I haven't tried to recompile with /usr/src/linux pointing to 2.2.12 per
Darren's solution - that's my next thing to do, or perhaps compile
2001 Feb 10
2
SNAP 20010209 fails to compile sftp on Slackware
Yo All!
openssh-SNAP-20010209.tar.gz fails to compile on Slackware. Patch at
the end of this message.
Here is the error:
gcc -o sftp sftp.o sftp-client.o sftp-common.o sftp-int.o log-client.o -L. -Lopenbsd-compat/ -L/usr/local/ssl/lib -L/usr/local/ssl -lssh -lopenbsd-compat -lcrypt -lz -lnsl -lutil -lcrypto -lwrap
openbsd-compat//libopenbsd-compat.a(bsd-arc4random.o): In function
2012 Aug 05
2
[Bug 2030] New: build of 6.0p1 fails @ "/usr/bin/ld: unrecognized option '-Wl,-rpath,/usr/local/ssl/lib64"
https://bugzilla.mindrot.org/show_bug.cgi?id=2030
Priority: P5
Bug ID: 2030
Assignee: unassigned-bugs at mindrot.org
Summary: build of 6.0p1 fails @ "/usr/bin/ld: unrecognized
option '-Wl,-rpath,/usr/local/ssl/lib64"
Severity: major
Classification: Unclassified
OS: Linux
Reporter:
2001 Sep 29
0
configure.in fixes for 2.9.9p2
configure.in patches for 2.9.9p2:
1. Allow --with-pcre to take a path specifying the root of the
PCRE install (ROOT/include, ROOT/lib)
2. Ditto for --with-zlib
3. $no_libnsl and $no_libsocket can be determined programmatically
4. Check for innetgr, getspnam, and util in the default $LIBS before
checking in -lrpc, -lgen, and -lutil, respectively
5. dirname() is in -lgen on some
2001 Aug 18
0
installing openssh-2.9p2 after openssl-0.9.6b on freebsd-4.3-RELEASE
hi.
please cc comments 2 me, i'm not subscribed.
what i did is simply this (you might have guessed :)
i had to install the improved version of openssl after recent, urgent
improvements. with this came came the urgent desire for openssh-CURRENT,
which had to be reinstalled, because an old(?) version comes with the
distribution.
here's the diff. spare me and yourselfs a desciption of
2011 Mar 04
3
[Bug 1875] New: Gentoo QA warning: net-misc/openssh-5.8_p1-r1: closefromtest.c:46: warning: implicit declaration of function ‘closefrom’
https://bugzilla.mindrot.org/show_bug.cgi?id=1875
Summary: Gentoo QA warning: net-misc/openssh-5.8_p1-r1:
closefromtest.c:46: warning: implicit declaration of
function ?closefrom?
Product: Portable OpenSSH
Version: 5.8p1
Platform: All
OS/Version: Linux
Status: NEW
Severity: minor
2019 Apr 05
0
Make/Build Error on armhf
Hi Dirk.
Ok, now im ready with the debian packages for 4.10, this could make your life more easy.
I've not tested this but should work, you could try this.
Install a debian 9 server as minimal as possible, so choose expert install, only install ssh server, nothing else.
Now in this order, start building the armhf samba 4.10 packages
This should be easy todo now since i've match the
2019 Apr 02
2
Make/Build Error on armhf
Hello Norbert,
thanks for your reply. Does that mean that the rpi build environment is not uptodate?
-----Ursprüngliche Nachricht-----
Von: samba <samba-bounces at lists.samba.org> Im Auftrag von Norbert Hanke via samba
Gesendet: Dienstag, 2. April 2019 21:28
An: samba at lists.samba.org
Betreff: Re: [Samba] Make/Build Error on armhf
Hi,
I noticed the same, actually with many more shared
2006 May 09
1
xmalloc symbol in libssh
Hi list,
(Please Cc: me in your replies because I'm not subscribed to this list.)
While trying to build lukemftpd staticaly on FreeBSD, I got a link-time
error. Libssh.a indeed provides the "xmalloc" symbol (I suppose there
are more). I wonder if this is whether intentional or not. It is a
very common function name, and I think it would be worth renaming
it to something like
2000 Aug 06
1
problems compiling sshd on slackware 7.x
Hi,
I tried to compile openssh-2.1.1p4 on a slackware 7.1 (and then on a
slackware 7.0). you need to supply -lcrypt because otherwise
auth-passwd.c line 135 calls the wrong crypt and sshd will never let
you log in. (took a while to figure that out.)
I tried './configure --with-libs crypt' but
configure doesn't seem to understand me ;)
checking host system type... Invalid