Afaik opengl extensions don't have a library, only header file. If extension is supported by your driver, then function is declared within opengl library (-lopengl), without separate library.
If you want to be able to use extensions easily (and want code to be portable to windows), you should use ether GLEE
. However, you can work without them - you simply need to #include glext.h AND #define corresponding GL_VERSION level before that include. This is not portable and won't work on Windows(because OpenGL support on windows is crap - by default windows libopengl library (or opengl32.lib) has support for OpenGL 1.1 functions only(which is problem) - so you won't get anywhere without extension library on windows - you'll need to do a lot of wglGetProcAddress calls(you can see that in exapmle)).
Note that glPointParameter is part of OpenGL standard since version 1.4 and normally (on linux) don't need extension. To use it on linux either use
and link to libopengl.
or use glee or glew library (see which has better license).
Either of them won't work if your videocard/driver doesn't support OpenGL 1.4 or corresponding extension.
Personally, I prefer "billboards" (camera aligned squares with textures - using shaders(which is better) or manually(which is slower)) to pointsprites, because point-spirtes has maximum size limitation, there will be a trouble if you change camera FOV (you'll need to recalculate attenuation), you can't rotate them (clockwise/counterclockwise) and when I worked with pointsprites last time (few years ago, on DirectX) ATI cards (Radeon 9000 at that time) had buggy pointsprite support so they didn't support attenutations at all with certain techniques. Also, you don't need extensions to create billboards - every card with texturing support will do.
On other hand, managing pointsprites is easier and you can get rid of attenuations by writing vertex shader which will calculate point size according to current projection matrix, point size and position. Unfortunately I haven't done that in OpenGL, so I simply don't remember if pointsize is available within shader (in OpenGL) and can be changed by shader or not. Also, although such shader is possible, it won't solve all possible problems with pointsprites - AFAIK pointsprite is always square which can be a problem. Also, GLSL (shader language) requires OpenGL 2.0 or 1.5 with extensions, which can be too much for basic application.
In short - if you want to use GL extensions in easy/portable way - use either GLEE or GLEW library.