On Tue, 10 Feb 2009 20:52:36 -0600, Chris Bagwell wrote:
> > 1. I have to run make again and again because I get many errors
> > mv: .deps/xxx.Tpo: No such file or directory
> > xxx is a placeholder for various filenames. Maybe a timing issue.
> > I don't know
>
>
> I think if you add --disab
On Thu, 05 Feb 2009 18:14:00 -0600, Chris Bagwell wrote:
...
> ... Also, another thing to try for the heck of it is
> "./configure --disable-shared --enable-static" and see if it works in
> that mode.
Finally I tried with
configure with --disable-shared --enable-static
This works ( I get a hu
On Tue, Feb 10, 2009 at 2:45 PM, Franz Bakan wrote:
> On Thu, 05 Feb 2009 18:14:00 -0600, Chris Bagwell wrote:
>
> ...
> > ... Also, another thing to try for the heck of it is
> > "./configure --disable-shared --enable-static" and see if it works in
> > that mode.
>
> Finally I tried with
> conf
Hi,
On Sat, 07 Feb 2009 12:41:41 -0600, Chris Bagwell wrote:
> Can you email me the old patched libtool? Perhaps I can forward port
> what ever OS/2 changes to latest libtool for you.
...
> Can you log the output of each failed run to me? I'd like to see the
> filenames that are failing to se
Franz Bakan wrote:
> I built again and zipped the result.
>
> you can get it here:
>
> http://www.fbakan.de/temp/Sane-OS2-Build.zip
>
> The zip-file contains the generated libtool, the main Makefile,
> the output from configure and make stdout (.1) and stderr (.2)
> and the old os2-specific-libtoo
Franz Bakan wrote:
> The way to build on OS/2 was to run configure and then
> replace the autogenerated libtool with a rather old version
> of libtool (once patched by Yuri Dario some years ago).
>
> This always worked.
>
Can you email me the old patched libtool? Perhaps I can forward port
wha
Hi,
> Anyone with access to OS/2, please try out current CVS.
>
> I've reverted back to -version-info with libtool; same as 1.0.19.
I'm very sorry, but I forgot to mention important details
in my last mail about the problems with libtool when
compiling Sane on OS/2 after the latest changes in C
Anyone with access to OS/2, please try out current CVS.
I've reverted back to -version-info with libtool; same as 1.0.19.
Chris
Chris Bagwell wrote:
Hi,
>> -rpath $(libdir) -version-number
>> $(V_MAJOR):$(V_MINOR):$(V_REV)
>>
>> From my 1.0.19 build:
>>
>> -rpath $(libdir) -version-info $(V_MAJOR):$(V_REV):$(V_MINOR)
>
> Hmm, thats a difference between 1.0.19 and CVS... When the hard c
Chris Bagwell writes:
> Olaf Meeuwissen wrote:
>> Oops! I just realised that the code I was looking at was **after**
>> `autoreconf --force --install`. The code in CVS is 11 months old and
>> does NOT have a wildcard that would match 'os2'.
>>
>> The CVS version has:
>> VERSION=1.5.22
>> TI
Chris Bagwell writes:
> Olaf Meeuwissen wrote:
>> Based on the libtool/ltmain.sh code from the CVS snapshot (2009-02-05),
>> I would expect CURRENT to have a value of 2 (1 on FreeBSD and SunOS).
>> You get an empty string. The '1:1:0' version information looks fine
>> to me.
>
> I do not see "os
Julien BLACHE wrote:
> Chris Bagwell wrote:
> -rpath $(libdir) -version-number
> $(V_MAJOR):$(V_MINOR):$(V_REV)
>
>
> From my 1.0.19 build:
>
> -rpath $(libdir) -version-info $(V_MAJOR):$(V_REV):$(V_MINOR)
>
Hmm, thats a difference between 1.0.19 and CVS... W
"Franz Bakan" writes:
> Hi,
>
> After the latest modifications with the libtool stuff I now get this error:
>
> [snip]
> make[1]: Entering directory `G:/src/432/sane-backends/backend'
> sh ../libtool --silent --tag=CC --mode=link gcc -D__EMX__ -DOS2
> -D__ST_MT_ERR
> NO__ -fno-omit-frame-poin
Chris Bagwell wrote:
Hi,
> libsane.la: dll.lo dll-s.lo $(EXTRA) $(addsuffix .lo,$(DLL_PRELOAD))
> $(LIBOBJS)
> @$(LIBTOOL) $(MLINK) $(CC) -o $@ $(LDFLAGS) $(BACKENDLIBS) $^ \
> $(addsuffix .lo,$(DLL_PRELOAD_EXTRAS)) @LIBTOOL_LINK_EXTRA@ \
> -rpath $(libd
Hi,
After the latest modifications with the libtool stuff I now get this error:
...
Making all in backend
make[1]: Entering directory `G:/src/432/sane-backends/backend'
sh ../libtool --silent --tag=CC --mode=link gcc -D__EMX__ -DOS2 -D__ST_MT_ERR
NO__ -fno-omit-frame-pointer -O2 -W -Wall -Wcas
Olaf Meeuwissen wrote:
>
> From the libtool --help --mode=link output:
>
> -no-undefined declare that a library does not refer to external symbols
>
> I fail to see how that has anything to do with the library version.
>
>
To tell you the truth, I don't understand -no-undefined... but from
Can you update to current CVS and try again? I went ahead and added
-no-undefined for OS/2 to help speed things along. I'm 99% sure its
needed. As a bonus it has latest libtool which may fix an OS/2 bug or two.
Chris
Franz Bakan wrote:
> Hi,
>
> After the latest modifications with the libtoo
Olaf Meeuwissen wrote:
> Oops! I just realised that the code I was looking at was **after**
> `autoreconf --force --install`. The code in CVS is 11 months old and
> does NOT have a wildcard that would match 'os2'.
>
> The CVS version has:
> VERSION=1.5.22
> TIMESTAMP=" (1.1220.2.365 2005/12/1
Olaf Meeuwissen wrote:
> "Franz Bakan" writes:
>
>
>> Hi,
>>
>> After the latest modifications with the libtool stuff I now get this error:
>>
>> [snip]
>> make[1]: Entering directory `G:/src/432/sane-backends/backend'
>> sh ../libtool --silent --tag=CC --mode=link gcc -D__EMX__ -DOS2
>> -D
Olaf Meeuwissen wrote:
> Based on the libtool/ltmain.sh code from the CVS snapshot (2009-02-05),
> I would expect CURRENT to have a value of 2 (1 on FreeBSD and SunOS).
> You get an empty string. The '1:1:0' version information looks fine
> to me.
>
I do not see "os2" listed in that general are
Can you give me a few pointers on timeframe of "latest modifications"?
I think you mean the addition of backend/Makefile.am in last 2 weeks but
want to be sure.
I'm reviewing old backend/Makefile.in and old libtool that was
generated. It looks like -version-number was always passed into libto
21 matches
Mail list logo
