On Thu, 7 Sep 2006 18:09:16 -0700, Steve Langasek <[EMAIL PROTECTED]> said:
> The other alternative discussed on IRC was to make /usr/lib/libfl.so
> a linker script, à la libc.so. I think the below should be
> sufficient, giving you PIC code when shared linking is requested by
> the linker and n
On 9/5/06, Manoj Srivastava <[EMAIL PROTECTED]> wrote:
I was initially going to just provide libfl.a with position
independent code, which would have prevented the FTBS breakage for
scanner containing shared libraries, at the expense of a register
lost for binaries that were otherwise
On Thu, Sep 07, 2006 at 02:45:50PM -0500, Bill Allombert wrote:
> So if you are to write a library that include a flex scanner, all you
> have to do is to prvide your own yywrap() function, even if it is
> just return 1; and you won't need to link with libfl.a.
Why can't flex emit a default yywra
On Tue, Sep 05, 2006 at 04:50:24PM -0500, Manoj Srivastava wrote:
>
> Starting with version 2.5.31-18 of flex we have started
> providing a static library compiled with position independent code,
> namely, libfl_pic.a, in addition to the normal libfl.a library. This
> is my mail, in acc
On Tue, Sep 05, 2006 at 04:50:24PM -0500, Manoj Srivastava wrote:
> Hi,
>
> Starting with version 2.5.31-18 of flex we have started
> providing a static library compiled with position independent code,
> namely, libfl_pic.a, in addition to the normal libfl.a library. This
> is my mail,
Manoj Srivastava writes ("Linking a static library with -fPIC for flex"):
> I was initially going to just provide libfl.a with position
> independent code, which would have prevented the FTBS breakage for
> scanner containing shared libraries, at the expense of a register
> lost for bina
6 matches
Mail list logo
