From: Dariusz Swiderski <sfires@sfires.net>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] cvs software issues
Date: Tue, 30 Mar 2004 12:10:19 +0200 [thread overview]
Message-ID: <4069478B.2070401@sfires.net> (raw)
In-Reply-To: <1080561659.2281.236.camel@pegasus>
Marcel Holtmann wrote:
> Hi Dariusz,
>
>
>>>it should create it if it is missing.
>>
>>apparently it doeas not:
>>sfires@snoopy:/home/storage/software/cvs/bluez/libs2$ ./bootstrap
>>configure.in: installing `./install-sh'
>>configure.in: installing `./mkinstalldirs'
>>configure.in: installing `./missing'
>>configure.in:19: installing `./config.guess'
>>configure.in:19: installing `./config.sub'
>>configure.in:19: required file `./ltmain.sh' not found
>>compat/Makefile.am: installing `./depcomp'
>>
>>im not very goot with automake and autoconf sripts, but in utils and libs
>>this file, is pulled from cvs, and yes, i have seen the remark in attic ;)
>
>
> it says so, but does this mean that it is not created ;)
ok, i see you are trying to pull my leg..:
sfires@snoopy:/home/storage/software/cvs/bluez/libs2$ ls
AUTHORS CVS/ Makefile.am README bootstrap* config.h.in debian/ install-sh* mkinstalldirs*
COPYING ChangeLog Makefile.in aclocal.m4 compat/ config.sub* depcomp* lib/ test/
COPYING.LIB INSTALL NEWS autom4te.cache/ config.guess* configure.in include/ missing*
the mkinstalldir and so on are in place, but not the ltmain.sh
>>>There is no planned coexisting of both version and if libs2 and utils2
>>>are ready for rollout it will replace the old one.
>>
>>ok, i can live with this, but what about hcid? its not in utils2
>
> I am not quite sure about the real future of hcid. We will have a
> replacement for it, but I want to redesign some parts of it.
ok, no problem, but there must be sth. to work with the pin-helper ;)
---snip---
> At the moment nobody. So feel free to take the code and clean it up and
> make it libs2 compatible.
so i will
greets
--
Maciej 'sfires' Swiderski
---------------------------------------------------
SysAdm | SecOff | DS14145-RIPE | DS11-6BONE
193.178.161.0/24 | 3ffe:8010:7:2a::/64 | AS16288
---------------------------------------------------
A mouse is a device used to point at the xterm you want to type in.
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2004-03-30 10:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-28 23:26 [Bluez-devel] cvs software issues Dariusz Swiderski
2004-03-29 10:44 ` Marcel Holtmann
2004-03-29 11:55 ` Dariusz Swiderski
2004-03-29 12:00 ` Marcel Holtmann
2004-03-30 10:10 ` Dariusz Swiderski [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=4069478B.2070401@sfires.net \
--to=sfires@sfires.net \
--cc=bluez-devel@lists.sourceforge.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