Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fails to build from source on GNU/kFreeBSD because of -R link option #5393

Closed
vicuna opened this Issue Nov 1, 2011 · 7 comments

Comments

Projects
None yet
1 participant
@vicuna
Copy link
Collaborator

vicuna commented Nov 1, 2011

Original bug ID: 5393
Reporter: @glondu
Assigned to: @protz
Status: closed (set by @protz on 2011-12-21T15:56:53Z)
Resolution: fixed
Priority: normal
Severity: block
Version: 3.12.1
Fixed in version: 3.13.0+dev
Category: ~DO NOT USE (was: OCaml general)
Monitored by: @protz @xclerc @damiendoligez

Bug description

The summary is self-explanatory... attached is a patch that makes the Debian package compile again.

File attachments

@vicuna

This comment has been minimized.

Copy link
Collaborator Author

vicuna commented Dec 21, 2011

Comment author: @protz

Xavier, any objections to my merging this? Stéphane, can you maybe add a comment saying what the -R option does and why it makes things fail on kFreeBSD? (I'm not familiar of kFreeBSD, sorry).

@vicuna

This comment has been minimized.

Copy link
Collaborator Author

vicuna commented Dec 21, 2011

Comment author: @glondu

I haven't found any documentation for -R. It is added only on BSD systems (and not on e.g. GNU).

This option has been introduced in commit 9072 (in 2008) by doligez, and it looks like it sets RPATH, so an equivalent could be -Wl,-rpath= (untested). However, this would go against Debian policy, since libX11 is in a standard location (my guess is that libX11 is in a location that is not searched by default by the dynamic linker on BSD). I doubt anyone would want to run GNU/kFreeBSD with a libX11 that is not in a standard location, though, since it mimics GNU for userland... so I would drop the option for the same reasons it is not given in the other GNU cases.

@vicuna

This comment has been minimized.

Copy link
Collaborator Author

vicuna commented Dec 21, 2011

Comment author: @protz

After reading http://gcc.gnu.org/faq.html I'm even more confused. Damien, any thoughts on this?

@vicuna

This comment has been minimized.

Copy link
Collaborator Author

vicuna commented Dec 21, 2011

Comment author: @xclerc

I have no clue about this one, but can play with
some virtualization tool if needed.

@vicuna

This comment has been minimized.

Copy link
Collaborator Author

vicuna commented Dec 21, 2011

Comment author: @protz

After chatting with Damien, your fix sounds just fine. Committed in svn r11925.

Thanks!

jonathan

@vicuna vicuna closed this Dec 21, 2011

@vicuna

This comment has been minimized.

Copy link
Collaborator Author

vicuna commented Jan 31, 2012

Comment author: @damiendoligez

This is all caused by a bug in GNU's config.guess: it is supposed to output at triplet, but on Ubuntu it outputs: i686-pc-linux-gnu, which is a quadruplet.

This potentially breaks all the "case" statements that try to match one member of the triplet.

This should probably be reported to the maintainers of autoconf and/or ubuntu.

@vicuna

This comment has been minimized.

Copy link
Collaborator Author

vicuna commented Jan 31, 2012

Comment author: @damiendoligez

After a look at config.guess, it seems to be broken as designed, no point in reporting it.

@vicuna vicuna added the bug label Mar 20, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.