Well, I haven't found the cause of this yet, but here's a test case.
It is fun to do ar -t libbar.a and see:
__.SYMDEF SORTED
libfoo.a
bar.o
libfoo.a
because every libbar.a needs two libfoo.a's!
Reported by Daniel Macks from the fink project, but reproducible on
linux as well as darwin.
I'
Gcj isn't available for compile-and-link test when building libjava.
I found a solution, which is to add a ltgcc.m4 file to the toplevel,
where we can override macros as we wish. For example, you can put a
copy of the Java configuration macro there with your hack. I will
approve such a patc
On Tue, May 29, 2007 at 07:33:28PM -0400, [EMAIL PROTECTED] wrote:
>
> On Tue, 29 May 2007 12:36:13 -0600, "Tom Tromey"
> said:
> > > "Charles" == Charles Wilson writes:
> > Charles> Secondly, the entire contents of libjava/libltdl/ need to be
> > Charles> updated.
> >
> > I don't think we n
On Tue, 29 May 2007 12:36:13 -0600, "Tom Tromey"
said:
> > "Charles" == Charles Wilson writes:
> Charles> Secondly, the entire contents of libjava/libltdl/ need to be
> Charles> updated.
>
> I don't think we need to do this. libgcj uses libltdl primarily as a
> portable wrapper for dlopen.
> "Charles" == Charles Wilson <[EMAIL PROTECTED]> writes:
I trimmed the CC list a bit.
Charles> Secondly, the entire contents of libjava/libltdl/ need to be
Charles> updated.
I don't think we need to do this. libgcj uses libltdl primarily as a
portable wrapper for dlopen. As such it works
H. J. Lu writes:
> On Tue, May 29, 2007 at 05:06:45PM +0200, Paolo Bonzini wrote:
> >
> > Certainly. Any compile-and-link tests won't work.
> > >>>I'm sorry, I missed the "and link" part of your question. Configury
> > >>>tests of this kind really aren't going to work. For things like
On Tue, 29 May 2007, Andrew Haley wrote:
> > Bulding an XXX language run-time library is a very special case. You
> > can't build an XXX language run-time library, assuming the XXX language
> > compiler is fully functional. If upstream libtool can support it, it
> > is great. Otherwise, we ha
On Tue, May 29, 2007 at 04:09:22PM +0100, Andrew Haley wrote:
> Paolo Bonzini writes:
> >
> > Certainly. Any compile-and-link tests won't work.
> > >>> I'm sorry, I missed the "and link" part of your question. Configury
> > >>> tests of this kind really aren't going to work. For things
Paolo Bonzini writes:
>
> Certainly. Any compile-and-link tests won't work.
> >>> I'm sorry, I missed the "and link" part of your question. Configury
> >>> tests of this kind really aren't going to work. For things like tests
> >>> for PIC, it's pointless: gcj supports the same option
On Tue, May 29, 2007 at 05:06:45PM +0200, Paolo Bonzini wrote:
>
> Certainly. Any compile-and-link tests won't work.
> >>>I'm sorry, I missed the "and link" part of your question. Configury
> >>>tests of this kind really aren't going to work. For things like tests
> >>>for PIC, it's pointle
Certainly. Any compile-and-link tests won't work.
I'm sorry, I missed the "and link" part of your question. Configury
tests of this kind really aren't going to work. For things like tests
for PIC, it's pointless: gcj supports the same options as gcc.
Then, does anybody know the very reason w
On Tue, May 29, 2007 at 04:49:11PM +0200, Paolo Bonzini wrote:
>
> > > Certainly. Any compile-and-link tests won't work.
> >
> >I'm sorry, I missed the "and link" part of your question. Configury
> >tests of this kind really aren't going to work. For things like tests
> >for PIC, it's pointless
> Certainly. Any compile-and-link tests won't work.
I'm sorry, I missed the "and link" part of your question. Configury
tests of this kind really aren't going to work. For things like tests
for PIC, it's pointless: gcj supports the same options as gcc.
Then, does anybody know the very rea
On Tue, May 29, 2007 at 04:21:22PM +0200, Paolo Bonzini wrote:
>
> >>It doesn't work since gcj isn't functional at that time. configure
> >>complains
> >>
> >>configure:16060: /export/build/gnu/gcc-isa/build-x86_64-linux/gcc/gcj
> >>-B/export/build/gnu/gcc-isa/build-x86_64-linux/x86_64-unknown-li
It doesn't work since gcj isn't functional at that time. configure
complains
configure:16060: /export/build/gnu/gcc-isa/build-x86_64-linux/gcc/gcj
-B/export/build/gnu/gcc-isa/build-x86_64-linux/x86_64-unknown-linux-gnu/libjava/
-B/export/build/gnu/gcc-isa/build-x86_64-linux/gcc/ -c -O2 -g -O2
On Tue, May 29, 2007 at 06:47:07AM -0700, H. J. Lu wrote:
> On Tue, May 29, 2007 at 09:07:49AM +0200, Paolo Bonzini wrote:
> >
> > >This patch allows me to run aclocal and autoconf. However, it still
> > >doesn't work. But we can't use conftest* as Java class file name since
> > >it will be remove
On Tue, May 29, 2007 at 09:07:49AM +0200, Paolo Bonzini wrote:
>
> >This patch allows me to run aclocal and autoconf. However, it still
> >doesn't work. But we can't use conftest* as Java class file name since
> >it will be removed after a test is done. That means the second gcj
> >test will fail
This patch allows me to run aclocal and autoconf. However, it still
doesn't work. But we can't use conftest* as Java class file name since
it will be removed after a test is done. That means the second gcj
test will fail since those class files have been removed. If we
rename them to something
18 matches
Mail list logo
