This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Adding a file to libgomp


Amittai Aviram <amittai.aviram@yale.edu> writes:

> 2.  I changed the value of the definition of _GCC_AUTOCONF_VERSION from 2.64 to 2.65.  (Otherwise, automake fails and complains that aclocal.ac was made with autoconf version 2.64.)

Actually, don't do that.  Instead, download autoconf 2.64, build and
install it in a local directory, and use that to rebuild the configure
script.  Similarly, you must use automake 1.11.1.

These specific version dependencies are the reason why the files are not
rebuilt by default.


> I then cd'd to my build directory, configured, and built:
>
> ~/gcc $ cd ../gcc_obj
> ~/gcc_obj $ ../gcc/configure --prefix=/<myhomedir>/gcc_install
> ...
> ~/make -j && make -j install
>
> However, after all that, the name of the function defined in my new file does not occur in the compiled library code, as I discovered by using nm libgomp | grep "my_new_function" .
>
> Is there something else I'm supposed to do between running automake and building the project with configure, make, and make install?

Take a look at libgomp.map.  You may need to add your new symbol there.
If this is not for your own private use, add the new symbol under a new
version string.

Ian


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]