Hi,
gcc-4.0 now provides support for controlling the set of symbols exported
from a shared library in a reasonable, maintainable way. I have added a
gnulib module to this effect. With documentation, this time :-)
Bruno
= modules/visibility
Bruno Haible <[EMAIL PROTECTED]> writes:
> Hi,
>
> gcc-4.0 now provides support for controlling the set of symbols exported
> from a shared library in a reasonable, maintainable way. I have added a
> gnulib module to this effect. With documentation, this time :-)
How does this relate to something
Simon Josefsson wrote:
> > gcc-4.0 now provides support for controlling the set of symbols exported
> > from a shared library in a reasonable, maintainable way. I have added a
> > gnulib module to this effect. With documentation, this time :-)
>
> How does this relate to something like Libtool's -e
On Mon, Jul 25, 2005 at 05:46:02PM +0200, Bruno Haible wrote:
> Simon Josefsson wrote:
> > Your module look somewhat gcc-specific, whereas, in theory,
> > libtool might work with other compilers too.
>
> Do you know of other compilers than GCC 4 and MSVC that support the
> equivalent of "-fvisibil
Hi,
I'm including a patch for regex.m4. I replaced AC_TRY_RUN with
AC_RUN_IFELSE and removed the use of m4_syscmd/m4_sysval.
The program was wrapped in [[ ... ]] which caused an error on Mac OS/X
10.3 with recent versions of autoconf/make/libtool (2.59, 1.9.6, 1.5.8,
resp.). I added AC_LANG
Bruno Haible <[EMAIL PROTECTED]> writes:
> Simon Josefsson wrote:
>> > gcc-4.0 now provides support for controlling the set of symbols exported
>> > from a shared library in a reasonable, maintainable way. I have added a
>> > gnulib module to this effect. With documentation, this time :-)
>>
>> Ho
Albert Chin wrote:
> The AIX v7 compiler compiles the following:
> $ cat vis.c
> extern __attribute__((__visibility__("hidden"))) int hiddenvar;
> extern __attribute__((__visibility__("default"))) int exportedvar;
> extern __attribute__((__visibility__("hidden"))) int hiddenfunc (void);
> extern
"James Gallagher" <[EMAIL PROTECTED]> writes:
> I added AC_LANG_SOURCE to fix the error and figured I might as well
> make the switch to RUN_IFELSE at the same time since the docs say
> TRY_RUN is obsolete.
That makes sense, yes. I installed the patch below (plus some
unimportant indenting chang
>>> I removed m4_syscmd, ..., because they were not working on either Mac
>>> OS/X or RHEL3.
>>
>> Hmm, why not? Shouldn't they be working? What versions of m4 and
>> Autoconf
>> were you using? Let's try to see what the underlying problem is first,
>> before removing this from regex.m4.
>
> Wel
This module didn't take long to write, so I thought
I'd submit it before checking if it would be accepted
or not.
It "backports" the TEMP_FAILURE_RETRY macro from
GNU Libc to Gnulib.
Regards,
Oskar Liljeblad ([EMAIL PROTECTED])
diff -u1 ChangeLog.v0 ChangeLog
--- ChangeLog.v02005-07-26 0
"Oskar Liljeblad" <[EMAIL PROTECTED]> writes:
> It "backports" the TEMP_FAILURE_RETRY macro from
> GNU Libc to Gnulib.
The proposed implementation isn't portable; it assumes GCC syntax.
And it should probably defer to the unistd.h implementation if available.
My kneejerk reaction is that it's a
On Jul 25, 2005, at 3:49 PM, Paul Eggert wrote:
I removed m4_syscmd, ..., because they were not working on either
Mac
OS/X or RHEL3.
Hmm, why not? Shouldn't they be working? What versions of m4 and
Autoconf
were you using? Let's try to see what the underlying problem is
first,
before re
12 matches
Mail list logo